Releases: camptocamp/devops-stack-module-traefik
v9.0.2
v9.0.1
v9.0.0
9.0.0 (2024-10-09)
⚠ BREAKING CHANGES
- point the Argo CD provider to the new repository (#88)
Features
Migrate provider source oboukili
-> argoproj-labs
We've tested the procedure found here and we think the order of the steps is not exactly right. This is the procedure we recommend (note that this should be run manually on your machine and not on a CI/CD workflow):
-
First, make sure you are already using version 6.2.0 of the
oboukili/argocd
provider. -
Then, check which modules you have that are using the
oboukili/argocd
provider.
$ terraform providers
Providers required by configuration:
.
├── provider[registry.terraform.io/hashicorp/helm] 2.15.0
├── (...)
└── provider[registry.terraform.io/oboukili/argocd] 6.2.0
Providers required by state:
(...)
provider[registry.terraform.io/oboukili/argocd]
provider[registry.terraform.io/hashicorp/helm]
-
Afterwards, proceed to point *ALL the DevOps Stack modules to the versions that have changed the source on their respective requirements. In case you have other personal modules that also declare
oboukili/argocd
as a requirement, you will also need to update them. -
Also update the required providers on your root module. If you've followed our examples, you should find that configuration on the
terraform.tf
file in the root folder. -
Execute the migration via
terraform state replace-provider
:
$ terraform state replace-provider registry.terraform.io/oboukili/argocd registry.terraform.io/argoproj-labs/argocd
Terraform will perform the following actions:
~ Updating provider:
- registry.terraform.io/oboukili/argocd
+ registry.terraform.io/argoproj-labs/argocd
Changing 13 resources:
module.argocd_bootstrap.argocd_project.devops_stack_applications
module.secrets.module.secrets.argocd_application.this
module.metrics-server.argocd_application.this
module.efs.argocd_application.this
module.loki-stack.module.loki-stack.argocd_application.this
module.thanos.module.thanos.argocd_application.this
module.cert-manager.module.cert-manager.argocd_application.this
module.kube-prometheus-stack.module.kube-prometheus-stack.argocd_application.this
module.argocd.argocd_application.this
module.traefik.module.traefik.module.traefik.argocd_application.this
module.ebs.argocd_application.this
module.helloworld_apps.argocd_application.this
module.helloworld_apps.argocd_project.this
Do you want to make these changes?
Only 'yes' will be accepted to continue.
Enter a value: yes
Successfully replaced provider for 13 resources.
-
Perform a
terraform init -upgrade
to upgrade your local.terraform
folder. -
Run a
terraform plan
orterraform apply
and you should see that everything is OK and that no changes are necessary.
v8.2.0
v8.1.0
v8.0.0
8.0.0 (2024-08-15)
⚠ BREAKING CHANGES
- chart: major update of dependencies on traefik chart
- The v30 of the chart includes a breaking change because the values of the Gateway API implementation have changed. This change does not affect us directly on the DevOps Stack, and since this is a very new feature I do not see it affecting any of our deployments.
Features
- chart: major update of dependencies on traefik chart (1ba9afa)
v7.0.0
7.0.0 (2024-07-10)
⚠ BREAKING CHANGES
-
chart: major update of dependencies on traefik chart (#77):
-
- if you were overriding port exposure behavior using the
expose
orexposeInternal
flags, you should replace them with a service name to boolean mapping (check the official changelog for an example). - if you were previously using the
service.internal
value, you should migrate the values to theservice.additionalServices.internal
value instead; this should yield the same results, but make sure to carefully check for any changes! - resources that use the
traefik.containo.us
are definitely no longer supported; the other modules of the DevOps Stack have already been migrated, but make sure you make the changes on your side.
- if you were overriding port exposure behavior using the
-
- multiple CRDs have been updated but the users of the DevOps Stack do not need to update them manually since Argo CD takes care of it;
- the upstream team added the first experimental support for Traefik v3; a migration guide for your resources is available here;
- this upgrade also introduces support to OpenTelemetry; although this is not a breaking change, it is noteworthy;.
-
- there is change in the values that affects the way we activate the ServiceMonitor for Prometheus; we can now use an attribute
enabled
to activate it; see here; this was supported on our module with this change; - Kubernetes Gateway support is no longer experimental;
- the IngressRoute for the Traefik Dashboard is now disabled by default.
- there is change in the values that affects the way we activate the ServiceMonitor for Prometheus; we can now use an attribute
-