Open jaygridley opened 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
I am taking a look at this, the plan is to get back in a couple of days with a PR. Thanks!
What problem are you trying to solve?
After the split of crds and control-plan helm charts in https://github.com/linkerd/linkerd2/issues/6620, there is no mechanism for how to wait for crds to be present in the cluster when installing in an automated way.
For example, when installing both charts using Terraform Helm provider there is no deterministic approach how to detecting if crds are present in the cluster and subsequent control-plane installation could fail.
How should the problem be solved?
Kubernetes Job could be added that will check the Kubernetes API for CRDs presence and its status. Then Helm release could leverage
wait_for_jobs
attribute.Any alternatives you've considered?
N/A
How would users interact with this feature?
No response
Would you like to work on this feature?
maybe