Skip to content

Apply Add-Ons again after cluster upgrade#208

Closed
Nils98Ar wants to merge 12 commits intomainfrom
feat/cluster_addon_afterclusterupgrade
Closed

Apply Add-Ons again after cluster upgrade#208
Nils98Ar wants to merge 12 commits intomainfrom
feat/cluster_addon_afterclusterupgrade

Conversation

@Nils98Ar
Copy link
Member

@Nils98Ar Nils98Ar commented Mar 7, 2025

What this PR does / why we need it:

Apply cluster addons after cluster upgrade again to re-run templating with new K8s version.

As far as I understand it the templating is only done with the old K8s version otherwise (before K8s upgrade).

TODOs:

  • squash commits

jschoone and others added 12 commits February 27, 2025 08:12
Kubernetes versions come from
https://github.com/osism/k8s-capi-images

OCCM and Cinder-CSI versions come from
https://kubernetes.github.io/cloud-provider-openstack

Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
According to
https://github.com/SovereignCloudStack/minutes/blob/main/container/20250221.md
yawol and kube-vip will be removed.

Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
The values for the metrics server have changed and some are already
outdated.
This smaller version should to the same for this case.

Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
Even 1.17 is already available it needs some additional configuration
and would fail here.
Cilium 1.16.x is still supported so we are good here.

Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
Signed-off-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>
Signed-off-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>
Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
The Cluster Stack Operator has the `Multi Stage Addon` feature to
install addons in a specified order. This commit adds the configuration
to make use of it at least in a very simple way.

Signed-off-by: Jan Schoone <jan.schoone@uhurutec.com>
Signed-off-by: Nils Arnold <arnold@aov.de>
@jschoone jschoone force-pushed the refactor/modernize_scs_cluster_stacks branch 9 times, most recently from f610df5 to 3d34c07 Compare March 7, 2025 22:45
@jschoone
Copy link
Contributor

jschoone commented Mar 8, 2025

Hi @Nils98Ar, can you explain in the commit or description why this is needed and why it should be solved like this?
Because I'd suggest we check whether we directly find a solution in #211 (formerly part of #203)

@jschoone jschoone force-pushed the refactor/modernize_scs_cluster_stacks branch from 3f9366a to fbf6fe0 Compare March 10, 2025 11:38
Base automatically changed from refactor/modernize_scs_cluster_stacks to main March 10, 2025 11:39
@garloff garloff mentioned this pull request Aug 5, 2025
6 tasks
@garloff
Copy link
Member

garloff commented Dec 17, 2025

Is this still open?
Does #211 fail to address this?

@Nils98Ar
Copy link
Member Author

The idea was to add apply the AddOns after the cluster upgrade again in case of version specific helm templating for the new kubernetes version.

I am not sure if this case is adressed by the CSO maybe in a different way already.

@Nils98Ar
Copy link
Member Author

Already part of #255 for scs2/3.

@Nils98Ar Nils98Ar closed this Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants