search

stackabletech / issues

This repository is only for issues that concern multiple repositories or don't fit into any specific repository
2 stars 0 forks source link

Use the namespace stackable-operators in the SecretClass tls in the OLM package #498

Closed siegfriedweber closed 4 months ago

siegfriedweber commented 7 months ago

Use the namespace stackable-operators in the SecretClass tls in the OLM package

Currently the namespace default is set which means that the secret secret-provisioner-tls-ca is generated in the default namespace.

Installing via OLM requires the operators to be installed in the namespace stackable-operators because the ClusterRoleBinding of the secret-operator points to this namespace. Therefore, it is consequent to keep things together and also create the secret secret-provisioner-tls-ca in this namespace.

This is a breaking change which must be announced prominently. If pods would use different root CAs at the same time, they cannot communicate with each other anymore.

The Helm installation does not have a requirement on the namespace. It would be possible to also set the namespace in the SecretClass where the operator is installed to, but if the secret-operator will be installed in another namespace then running products would break. So we decided, to keep the default namespace for the Helm installation.

nightkr commented 5 months ago

The Helm installation does not have a requirement on the namespace. It would be possible to also set the namespace in the SecretClass where the operator is installed to, but if the secret-operator will be installed in another namespace then running products would break. So we decided, to keep the default namespace for the Helm installation.

IMO: The breaking rationale applies equally in both cases, but on Helm we can trivially put it in the target ns.

razvan commented 4 months ago

There is a PR that fixes this issue for the next SDP release.

I propose to move this issue to the track column until the next certification round.

adwk67 commented 4 months ago

Tested successfully on OKD/4.15.

razvan commented 4 months ago

This has beed shipped with 24.4.0-1

lfrancke commented 1 month ago

Sorry to bring this back from the dead, but: Do we have any migration documentation/release notes on this one?