Closed razvan closed 6 months ago
@razvan was https://github.com/stackabletech/issues/issues/498 solved in the previous release? That's a pretty breaking change and not something I'd be comfortable applying to a patch release.
@razvan was #498 solved in the previous release? That's a pretty breaking change and not something I'd be comfortable applying to a patch release.
it's ... complicated. This was correct (from the perspective of existing users) in 23.4.0, then broken in 23.11.0 and 24.3.0.
So I consider it a bug fix.
Should we announce this known bug on etc..discord and GitHub and what is the approximate timeline?
This is in done but there are a whole bunch of checklist items unchecked and it's not closed. Can you update the ticket?
Description
Note on the version: initially this release was meant to be named
24.3.0-1
but according to semver rules, this is a pre-release to24.3.0
and the operator certification pipeline rejects it. Therefore the decision was made to rename it to24.4.0-1
.It was discovered that the secret op is missing the permission to
update
secrets. ThisClusterRole
permission was added after23.11.0
and due to a mistake in the OLM generation process, it was lost in24.3.0
.This is a bug that prevents users of
23.11.0
to upgrade to24.3.0
Solution
Issue a bugfix "release" for the OLM packages and not a full SDP platform release.
This OLM release will be named
24.3.0-124.4.0-1
and will only exist in the certified operators repository.This release will:
update
rule onsecrets
to the ClusterRolenamespace
property of thetls
secretclass https://github.com/stackabletech/issues/issues/498dependency.yaml
metadata on commons, secret and listener ops24.3.0
but with OLM version24.3.0-1
skips: 24.3.0
in the CSVaddthis is not possiblereplaces: 23.11.0
in the CSVThis release will not:
Testing workflow
Checkout 24.3.0 tag in operator repo:
Create new branch (from main) in certified ops repo:
Generate 24.4.0-1 OLM manifests
Generate OLM bundles:
Generate or update the custom catalog:
Use the OperatorHub UI to install the operator.
Run the smoke test:
Done!