Cannot add infrastructure provider after the initial installation about cluster-api-operator HOT 9 CLOSED

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from cluster-api-operator.

Especially since the initial install doesn't really work as the cert isn't immediately ready, even if just because the cert-manager webhook isn't immediately ready, which in turn makes the CRDs not ready, which in double turn forces me to create these resources with an upgrade.

And deleting the helm secrets so helm thinks this is an installation doesn't work either, as now the cert-manager namespace fails, because it already exists (the pre-install hook doesn't seem to work, as I've had to create it manually).
Also this is kinda bad, as the cert-manager namespace get's deleted this way...

Did this chart ever work? The capi-system namespace also get's deleted somehow...

λ helm install --repo https://kubernetes-sigs.github.io/cluster-api-operator capi-operator cluster-api-operator -n capi-system --create-namespace --set cert-manager.enabled=true --set infrastructure=openstack --wait
Error: INSTALLATION FAILED: failed to create resource: Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s": dial tcp 10.109.5.128:443: connect: connection refused

# waited until cert-manager was ready

λ helm install --repo https://kubernetes-sigs.github.io/cluster-api-operator capi-operator cluster-api-operator -n capi-system --create-namespace --set cert-manager.enabled=true --set infrastructure=openstack --wait
Error: INSTALLATION FAILED: cannot re-use a name that is still in use

λ helm upgrade --repo https://kubernetes-sigs.github.io/cluster-api-operator capi-operator cluster-api-operator -n capi-system --create-namespace --set cert-manager.enabled=true --set infrastructure=openstack --wait
Release "capi-operator" has been upgraded. Happy Helming!
NAME: capi-operator
LAST DEPLOYED: Mon Oct 16 12:28:44 2023
NAMESPACE: capi-system
STATUS: deployed
REVISION: 2
TEST SUITE: None

# deleted helm secrets

λ helm install --repo https://kubernetes-sigs.github.io/cluster-api-operator capi-operator cluster-api-operator -n capi-system --create-namespace --set cert-manager.enabled=true --set infrastructure=openstack --wait
Error: INSTALLATION FAILED: failed pre-install: warning: Hook pre-install cluster-api-operator/templates/cert-manager.namespace.yaml failed: 1 error occurred:
	* object is being deleted: namespaces "cert-manager" already exists

λ helm install --repo https://kubernetes-sigs.github.io/cluster-api-operator capi-operator cluster-api-operator -n capi-system --create-namespace --set cert-manager.enabled=true --set infrastructure=openstack --wait
Error: INSTALLATION FAILED: cannot re-use a name that is still in use

# delete helm secrets again

λ helm install --repo https://kubernetes-sigs.github.io/cluster-api-operator capi-operator cluster-api-operator -n capi-system --create-namespace --set cert-manager.enabled=true --set infrastructure=openstack --wait
Error: INSTALLATION FAILED: failed post-install: warning: Hook post-install cluster-api-operator/templates/infra-conditions.yaml failed: 1 error occurred:
	* object is being deleted: namespaces "capi-system" already exists

from cluster-api-operator.

There is a limitation on Helm side for upgrades, we can't place CRDs in crds directory and Helm doesn't wait for CRDs to be registered on the upgrade(this seems to be intended). We have an issue #188 that suggests how upgrades can be fixed but currently, we only support installing providers on helm install command.

from cluster-api-operator.

we can't place CRDs in crds directory

Why not? 🤔

See duplicated explanation

from cluster-api-operator.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from cluster-api-operator.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from cluster-api-operator.

we can't place CRDs in crds directory

Why not? 🤔

See duplicated explanation

This is still needed

from cluster-api-operator.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

from cluster-api-operator.

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

from cluster-api-operator.