Enable users to customize BTP Operator secret and configMap #901
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
Description
We will allow to modify and keep user modifications in the btp-manager-secret.
Reason
Users wants to migrate btp-operator resources and configurations from one k8s cluster into new Kyma cluster.
AC:
sap-btp-manager
to skip reconciliation. If secret deleted then reconciliation is back.sap-btp-manager
secret is changed, immediately reconcile btp-operatorsap-btp-operator-clusterid
is always created and INITIAL_CLUSTER_ID from it is always in use. When pod will restart from 2.1 then btp-operator-controller will fail to start because CLUSTER_ID from CM != INITIAL_CLUSTER_ID from secret.panic: ClusterID changed, which is not supported. Please redeploy with --set cluster.id=test_cluster_id goroutine 1 [running]: main.main() /workspace/main.go:140 +0x1d65
sap-btp-operator-config
has new CLUSTER_ID set, restart sap-btp-operator-controller-manager-58fbb647ff-72ckx pods, checks ifsap-btp-operator-clusterid
is back with new INITIAL_CLUSTER_ID.Issue: End-to-end (e2e) integration test for customizing BTP Manager input secret #921
PR: E2E BTP Manager secret customization test #935
Agreed label name:
kyma-project.io/skip-reconciliation: 'true'
NOTE!:
The text was updated successfully, but these errors were encountered: