Repository navigation
platform: kubernetes-application has no dependsOn on keycloak-operator although its OIDC lifecycle needs it #4680
Description
packages/core/platform/sources/kubernetes-application.yaml lists its dependsOn (networking, the CAPI operator and providers, cozystack-engine) without keycloak-operator, while the tenant Kubernetes OIDC modes create Keycloak objects (the System/CustomConfig lifecycle exercised in hack/e2e-chainsaw/_lib/run-kubernetes.sh). Two consequences: on install the application can come up before the Keycloak CRDs exist, and the e2e selector, which walks these dependsOn edges, does not see that a change to system/keycloak or system/keycloak-operator affects kubernetes-latest. #4678 works around the selector side with an explicit mapping. Fix shape: add the dependsOn edge (only for the variants where OIDC is available), then drop the explicit selector mapping and let the graph carry it.
Activity
lexfrei commentedon Oct 2, 2026
Related stale comment:
hack/select-e2e.sharound lines 279-283 lists keycloak among engine dependencies that change no app's behaviour, which is false because of the tenant Kubernetes OIDC lifecycle. Worth fixing together with thedependsOnedge.test(e2e): cover monitoring OIDC modes with a Chainsaw suite (#4678)