-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm Chart CRDs Placement Causes Flaky Installations #534
Comments
This issue is currently awaiting triage. If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
We have verified that cluster-api-operator cannot be successfully installed by |
It won't work if you move it as it is because CRDs uses the go template. 😢 |
related to #188 |
Oh, Thx. |
/reopen I think it's still worth keeping open as the team considers the design of where CRDs are placed. |
@dtzar: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Okay👌 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What steps did you take and what happened:
Attempting to install the Helm chart for
cluster-api-operator
results in a flaky installation process. TheCRDs
are located in thetemplates/operator-components.yaml
file instead of thecrds
directory.What did you expect to happen:
The Helm install should complete successfully without errors.
Anything else you would like to add:
It is possible to separate the
CustomResourceDefinitions
from the other components using commands like the following:Can we consider reorganizing the files accordingly?
Environment:
kubectl version
):/etc/os-release
):/kind bug
[One or more /area labels. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]
Feel free to fill in the specific versions and any additional environment details before submitting the issue.
The text was updated successfully, but these errors were encountered: