k8s-ci-robot
commented
1 month ago 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.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
dtzar
What steps did you take and what happened: Deployed CAPI-operator see #532 and we discovered that part of the reason why the provider was failing to install was due to capi-operator being started, but not fully ready for the provider and then the provider fails to install. This was resolved by manually putting in a sleep job in helm.
What did you expect to happen: The capi-operator pods/services have a proper health/readiness check so that providers don't run into failure cases.
Environment:
kubectl version): 1.30.0/etc/os-release): WSL ubuntu 22.04/kind bug
Related to #532