You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit splits the cluster-api-operator Helm chart into two
separate charts to resolve flaky installations caused by webhook
validation timing issues.
Problem:
- Provider Custom Resources (CoreProvider, BootstrapProvider, etc.)
were applied at the same time as the operator deployment.
- The webhook service was not yet ready, leading to validation errors:
"no endpoints available for service 'capi-operator-webhook-service'".
Solution:
- Create two charts:
1. cluster-api-operator: contains only the operator deployment and
its resources.
2. cluster-api-operator-providers: contains all provider Custom
Resources.
- Installing the operator first allows the webhook to start before
provider CRs are applied.
Installation now requires:
1. Install operator:
helm install capi-operator capi-operator/cluster-api-operator \
--create-namespace -n capi-operator-system --wait --timeout 90s
2. Install providers:
helm install capi-providers \
capi-operator/cluster-api-operator-providers \
-n capi-operator-system \
--set infrastructure.docker.enabled=true \
--set cert-manager.enabled=true \
--set configSecret.name=${CREDENTIALS_SECRET_NAME} \
--set configSecret.namespace=${CREDENTIALS_SECRET_NAMESPACE}
Fixes: #534
Signed-off-by: kahirokunn <[email protected]>
0 commit comments