See the fragment files in the changelog.d/ directory.
-
Properly mirror the LMS caddy block in the default catch-all block used by
DRYDOCK_ENABLE_MULTITENANCY. -
Avoid retriggering the CONFIG_LOADED action multiple times when redering the jobs templates.
- The prefix
ingress-was removed from the ingress objects names. The suffix-tlswas also removed from additional ingresses defined viaDRYDOCK_INGRESS_EXTRA_HOSTS.
Warning
This rename will cause errors with the Ingress NGINX validation webhook due to two different ingress objects registering the same routes.
The old ingress objects must be deleted before applying the new
changes. Either perform a manual delete or set DRYDOCK_INGRESS to false
to delete all ingress objects in the next apply.
- The new
DRYDOCK_INGRESS_CLASSallows to configure the ingress class used by the Ingress and Issuers objects.
-
All support for debug pods via Ingress NGINX canary annotations has been removed. Users of this feature must re-implement it.
-
Several features that rely on specific ingress-nginx functionality have been removed:
- The NGINX static cache ingress resources and related plugin settings.
- The bypass Caddy configuration used to route traffic directly from the ingress-controller avoiding extra latency.
- Support for the Ulmo release
- Ensure that the
utf8mb4charset is used when connecting to MySQL. - Do not proxy SCORM assets directly through the LMS. This restores the previous behaviour for versions prior to v19.0.3 of openedx-scorm-xblock.
- Adjust the drop-db command to properly handle replica set configuration if available. Remove the Notes user if the Notes plugin is enabled.
- Avoid erroring when calling
iter_mfesif the MFE plugin is not enabled. Useful for testing with the minimal dependencies.
- Add the ability to exclude init jobs
- Add support for the Teak release
-
feat: create patch for registry credentials
-
feat: include json transform
-
feat: change secret render
-
fix: correct files
-
docs: update readmd
-
fix: include extra workloads
-
fix: change patch for cronjob and remove kind
-
docs: update readme.md
Co-authored-by: Moisés González moises.gonzalez@edunext.co
- fix: remove deamonset and statefulsets
The tutor-forum plugin hardcodes the value of the name of the forum database in the Django settings,
dropping the previous FORUM_MONGODB_DATABASE setting
(https://github.com/overhangio/tutor-forum/blob/5d3d2dd7d1ea3c9a311ac5619eb5931a111ba363/tutorforum/plugin.py#L29).
We reintroduce the FORUM_MONGODB_DATABASE setting and ensure the mongodb user has permissions over
the Forum Database.
In order to be able to override the hardcoded value we lower the priority level of the Drydock patches, guaranteeing that they are going to be applied after all the installed plugins.
- Sumac release
(
e42e001)
Empty commit to trigger a major version bump
-
Adding replicaset info to mongosh connection command. Adding mongodb port variable (#145,
8855736) -
Include the MongoDB port in the mongosh command (useful when running MongoDB in a different port)
- Include the replica set info in the mongosh command. It could be the case you aren't connected to a replica set primary but to a secondary one. If the replica set name is not specified, the mongosh command will fail since it is not possible to write to a secondary
The location of the uwsgi.ini file was changed in tutor==18.1.3 so we have to update the command run by the container. Additionally we remove an unused variable that was lingering.
-
fix: add readiness probe for lms/cms
-
fix: add affinity to spread lms/cms to multiple nodes
-
chore: remove readiness probe
-
fix: reduce startup probe period seconds
-
fix: gracefully kill uwsgi workers
-
fix: disable local file loggers
-
fix: disable logging
-
fix: reduce max unavailable to 0
-
fix: add liveness probe for cms and lms
-
fix: fail early on tracking logger removal
-
chore: remove rolling update options
-
fix: restore preStop hook
-
fix: use right host for cms livenessProbe
-
fix: use lms/cms host only
-
chore: restore prestopHook
fix: add readiness probe for lms
chore: remove startup probe and increase timeout of readiness probe
chore: restore startup probe
- fix: when using SCORM, S3_HOST must be used for alternative S3-compatible services
The HPA sync-wave patch includes annotations to indicate argocd in which order should the HPA
resources be applied in relation to the other resources. The argocd.argoproj.io/hook: Sync and
argocd.argoproj.io/hook-delete-policy: HookSucceeded annotations are used for ephemeral
resources (like jobs) and should not be used for the HPA resources.
fix: address PR suggestions
build: correct port and path for mfe tests
- Redwood upgrade
(
fd100ad)
BREAKING CHANGE: version 18
- Version 18
The S3Boto3Storage backend no longer accepts the argument bucket. Use bucket_name or the setting AWS_STORAGE_BUCKET_NAME instead: jschneier/django-storages#636
-
fix: solve error check k8s workflow
-
fix: define specific kubeconform version and include action on push
-
fix: extract and set kubernetes version from kubectl
-
fix: verify minio host is defined on scorm proxy
-
chore: refactor scorm template
docs: add documentation for ingress lm extra hosts
-
feat: add poddisruptionbudget patches
-
test: update pdb
-
test: include pdbs in patches
-
test: using kustomization
-
test: include in resources
-
fix: include conditional for mfe and forum
-
fix: correct endlines
-
feat: pdb value parametrizable
-
fix: delete undefined variable
-
fix: drydock variable names
-
fix: change comparison operator and pdb path
BREAKING CHANGE: Support to tutor v17
- Support to tutor v17
(cherry picked from commit ed8b57a0600913ea77de02bd995f6adc134f1446)
Include an initialization job similar to the MySQL one that creates a mongodb user with the necessary permissions. To simplify things a bit we use the same user for edxapp and forum and remove the need for the forum-overrides patch.
BREAKING CHANGE: Drops support to python 3.7
- Drops support to python 3.7
-
feat: support docker operations for image in drydock backups
-
fix: update image variable in defaults and jobs template
-
fix: update .gitignore
-
fix: using BACKUP_VARIABLE
-
fix: update readme
-
fix: update gitignore for /build/ folder
-
fix: update variables names and jumplines
-
fix: duplicate key
-
fix: include custom_storage_endpoint in aws block
-
fix: newlines control
-
fix: args for command
-
fix: environment azure variables
-
fix: include bucket path in all options
-
fix: delete databases variable
-
fix: update .sh
-
fix: update default shipyard-utils image
-
feat: install azcopy
-
feat: add new variables and conditionals for storage services
-
fix: include custom storage endpoint inside s3 conditional
-
feat: add variables and azcopy command
-
fix: update variable names
-
fix: storage system names
-
fix: default s3 value
-
fix: error in readme
-
update backup system variable name
-
fix: azure-blob conditional
-
Removing inexistent folder from github actions release flow (
81f3a06) -
Using Github PAT to bypass main branch protection (
ad40e6a)
- Replacing Kustomize JSON patches with strategic merge patches.
(
65a4b70)
Co-authored-by: Cristhian Garcia cristhian.garcia@edunext.co
Co-authored-by: Jhony Avella jhony.avella@edunext.co
-
fix: standarize whitespace triming
-
fix: define DJANGO_SETTINGS_MODULE for the cms debug pods
-
fix: use the DRYDOCK_CMS_SSO_USER variable on the init jobs
-
update forum job according to the k8s-jobs patch from tutor-forum. - use simplified hooks API introduced in tutor V15.3.0. - fix getting incompatible yaml files. - use DRYDOCK_CMS_SSO_USER variable instead of hard coded value.
This PR adds k8s templates for debug pods, i.e pods running with non-production setup (root user, container entrypoint/command changed, ...), which allow developers to debug services like LMS/CMS in a production-like environment.
This PR adds a list of jobs for the most used services. This list can be configured using a variable defined in the config.yml with optional services such as minio or forum; required services like LMS are not removable. We configured this behavior using waves from argoCD.
-
Add extra-jobs for extra tasks during initialization (#14,
bdfa07b) -
Removing MySQL jobs when MySQL running outside the cluster (#15,
fca2272)
-
feat: removing MySQL jobs when MySQL service is running outside the cluster
-
feat: adding labels to drydock jobs to better identify those from MySQL we want to skip
Starting HPA resources in wave 5 to make sure deployments already exist
- Setting a default value for DRYDOCK_NEWRELIC_CONFIG variable
(
a67dbf1)
The BaseManfests builder will render a standard Tutor environment based on the templates used in
version 13.3.1 of Tutor and use it as a base of Kustomization application with additional
resources as overlays.
The TutorExtendedConfig will return the Tutor configuration values of the current TUTOR_ROOT and
will use the default values of the template set (defined in a file defaults.yml) as a fallback.
-
Add kustomize based extensions to the base manifests (#3,
2b93163) -
Add newrelic manifests for tutor13 installation (#6,
8990e08) -
Add support for custom certificates (
809ae3e) -
Adding a better explanation at the readme (
95d1490) -
Adding readme (
86f1c66) -
Cleaning the manifest output a bit (
aa19367) -
Connecting with tutor (
76dec19) -
Laying the groundwork for the architecture (
bd6129c) -
Making all the classes be defined by the reference file (
138307a) -
Making reference support options (
7b69f2c) -
Making tutor_v13 volume sizes configurable (
6bbebca) -
Moving the tutor renderer to the actual implementing class (
e2a6119) -
Render global environment for prometheus outside tutor-env (#5,
f114243) -
Stating the purpose and context for this project (
2ba3280)