kubecf
kubecf copied to clipboard
Bump Eirini to 1.9.0
There's a new Eirini upstream version that comes with several bug fixes and improvements.
This bump should fix #1358 .
Once this is done, we can reactivate some of the CATS that we skip. This should be done as part of this card, so we can validate we're doing the right thing.
Please log the procedure to bump as part of this card and place it in docs.
We've been looking at bumping cf-deployment to v15.1. It fails with Eirini (v1.8) and @mook-as diagnosed:
... it looks like the /tasks endpoint was introduced in 2.0.0
So we may need to bump Eirini to 2.0.0 now. However, there are no images:
$ reg tags registry.suse.com/cap-staging/opi
INFO[0000] domain: registry.suse.com
INFO[0000] server address: registry.suse.com
1.5.0
1.6.0
1.7.0
1.8.0
1.8.0.1
1.9.0
latest
So how do we build the required images? Is there a pipeline somewhere?
Also, does anybody know already about any caveats or gotchas in bumping Eirini to 2.0.0 for kubecf?
Pinging @viovanov @jimmykarily @mudler (and if you know how to trigger the builds, please do so).
Things to watch for:
- This doesn't exist anymore: https://github.com/SUSE/catapult/blob/master/modules/tests/kubecf-test.sh#L206 (thus we don't need to skip it)
- We seem to skip this because rolling deployments don't work in kubecf. This should be fixed by adding the deployment updater. (eirini PT, kubecf issue)
- The pipeline that builds the Eirini images on SLE is red. It was working up to version 1.9 but broke for version 2.0. Needs fixing.
- The "legacy" staging (the non-kpack one), has been removed in version 2.0 (thus the major version bump). Bumping to that will probably not work unless we introduce kpack staging (because the endpoints for from the opi have also been removed). We probably won't be able to mix and match v2.0 components with v1.9 staging components.
These are all the things I could think of. Hope it helps.
We're checking if https://github.com/cloudfoundry-incubator/kubecf/issues/1547 is addressed by Eirini 1.9.
However, in light of Eirini 2.0, should we bump directly to that version?