Feat/new releases 202602

[garloff]

Update to latest k8s versions:

• v1.32.12 (w/ CSI 2.32.2 and OCCM 2.32.1)
• v1.33.8 (w/ CSI 2.33.1 and OCCM 2.33.1)
• v1.34.4 (w/ CSI 2.34.3 and OCCM 2.34.2)
• v1.35.1 (w/ CSI 2.35.0 and OCCM 2.35.0)

Add images info for 1.32.12, 1.33.7, 1.33.8, 1.34.4, 1.35.1.

Push csctl versions to publish k8s/ccsi/occm 1.34.4/2.34.3/2.34.2.

Pushed to registry for testing as openstack-scs2-1-34-v0-git-98555b0.
Will use branches to push 1-33 and 1-35.

[garloff]

Why is @schmidax not here?

[garloff]

Recreated as openstack-scs2-1-34-v0-git-bdddbeb. Previous version erroneously had included (outdated) helm chart and deployed an old OCCM. (It still appeared to work well.). Retesting now.

[gerbsen]

I'm removing me, since I really don't know what this is doing here. :/

[jschoone]

Thanks!

I recommend to keep the 1.35 still out even we have the .1 now.
The reason is the ongoing discussions on how we want to deal with breaking changes in #255. The idea of using the minor version for that seems to work very good for us. And now v1beta2 is around and the support for v1beta1 will be removed in capi 1.14 (August).
We then need to pin the capi version to <=1.13 to support the cluster-stacks with v1beta1.
For Kubernetes 1.34 it's only two months sind it's EOL in October, for 1.35 it would go until next years Februar.
The best solution seems to have the version dirs again. This looks wrong because of git but in this case it has a valid reason.
I created a possible structure in #259, also still draft because we test the workflows but that looks most promising imho

[garloff]

So, 3+3 Cluster with 1.34.4 created successfully, sonobuoy passed the e2e tests.

[garloff]

OK, so scs -> kubernetes v1.2x -- v1.32, scs2 -> v1.33, v1.34, scs3 -> 1.35+ ?

About directories: We have a mixture of things:

• Some data structures (versions.yaml, kubernetes.yaml) can support multiple parallel versions
• The files that csctl uses to create a release however can only cover one version

The mixture is not great.
For me, having separate subdirectories for each k8s minor version (even if only for csctl) would work fine.
I guess csctl would need some minor tweaks, so you can tell it which subdirectory to pick up when creating a cluster stack ...

[jschoone]

OK, so scs -> kubernetes v1.2x -- v1.32, scs2 -> v1.33, v1.34, scs3 -> 1.35+ ?

Basically yes

I guess csctl would need some minor tweaks, so you can tell it which subdirectory to pick up when creating a cluster stack ...

All instructions for csctl should already be inside the cluster stack directory, independent of its dirname.