Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update terraform-openshift4-exoscale to v6.0.0 #112

Merged
merged 2 commits into from
Feb 13, 2025
Merged

Update terraform-openshift4-exoscale to v6.0.0 #112

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
39a0e21
Update Exoscale Terraform module to v6.0.0
simu Feb 10, 2025
19fffc3
Add upgrade how-to for Exoscale
simu Feb 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion class/defaults.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ parameters:
multi_tenant: false
=_tf_module_version:
cloudscale: v4.5.2
exoscale: v5.4.0
exoscale: v6.0.0
images:
terraform:
image: registry.gitlab.com/gitlab-org/terraform-images/releases/terraform
Expand Down
23 changes: 23 additions & 0 deletions docs/modules/ROOT/pages/how-tos/upgrade-exoscale-to-v8.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
= Upgrade Exoscale clusters to component version v8

When upgrading to component version v8 for Exoscale clusters, the following breaking change requires manual changes in the Project Syn config of existing clusters:

* https://github.com/appuio/terraform-openshift4-exoscale/pull/98[Use instance pools for infra and worker node groups]

NOTE: We recommend applying the config changes outlined in this guide *before* upgrading to component version v8

TIP: We will publish a guide to migrate existing clusters to use instance pools in a future version of this component.

== Steps

. Get a clone of the tenant repo of the clusters that you want to upgrade to component version v8.

. Make sure component `openshift4-terraform` is updated to at least v7.6.0 so the variable `use_instancepools` exists

. Set `parameters.openshift4_terraform.variables.use_instancepools` to `false` for existing clusters.
+
TIP: If you're not planning to switch to instance pools for future clusters, you can set the variable for the whole tenant in `common.yml`.

. Commit the changes

Now you're ready to upgrade the component to v8 without changes to existing clusters.
1 change: 1 addition & 0 deletions docs/modules/ROOT/partials/nav.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@
* xref:how-tos/upgrade-exoscale-v3-v4.adoc[Upgrade Exoscale clusters from component version v3 to v4]
* xref:how-tos/upgrade-exoscale-v4-v5.adoc[Upgrade Exoscale clusters from component version v4 to v5]
* xref:how-tos/upgrade-exoscale-to-v7.adoc[Upgrade Exoscale clusters to component version v7]
* xref:how-tos/upgrade-exoscale-to-v8.adoc[Upgrade Exoscale clusters to component version v8]
* xref:how-tos/migrate-from-openshift4-cloudscale.adoc[Migrate from component `openshift4-cloudscale`]

.Technical reference
Expand Down
2 changes: 1 addition & 1 deletion tests/golden/exoscale/openshift4-terraform/openshift4-terraform/main.tf.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"ignition_ca": "SomeCertificateString",
"region": "ch-dk-2",
"rhcos_template": "my-iso-image",
"source": "git::https://github.com/appuio/terraform-openshift4-exoscale.git//?ref=v5.4.0",
"source": "git::https://github.com/appuio/terraform-openshift4-exoscale.git//?ref=v6.0.0",
"ssh_key": "ssh-ed25519 AA..."
}
}
Expand Down