-
Notifications
You must be signed in to change notification settings - Fork 11
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
"node-csr-approval" is not in the list of known controllers #193
Comments
Hi, this param appears here https://github.com/siderolabs/talos-cloud-controller-manager/blob/main/docs/deploy/cloud-controller-manager-edge.yml for How do you deploy the CCM ? |
I'm using Helmfile to deploy, with the following configuration entry: releases:
- name: talos-cloud-controller-manager
namespace: kube-system
chart: oci://ghcr.io/siderolabs/charts/talos-cloud-controller-manager
version: 0.4.0
values:
- ./chart-values/talos-ccm.yaml |
Thank you for feedback. Yap not I see what append here. I update the documentation and remove |
merged |
I deployed the helm chart 0.4.1 with the example values.yaml from the README.md
I get the same error as explained in the issue here: Environment
|
Hi, you force the list of controllers: enabledControllers:
- cloud-node
- node-csr-approval Documentation was updated recently for new (future) release. It will work for |
I see, i was missing that the changes are only deployed on the edge version. Thank you for the clarification. |
Bug Report
Description
With the most recent chart release, talos-ccm crash loops with the error message that it doesn't recognize the controller name. I figure it's because there wasn't a version released that included the code yet, although the chart is configured for it.
Logs
(I had to manually approve the node's CSR to get the logs, avoiding a catch-22 I found myself in before realizing that was an option. I thought I can't capture the logs as there is a TLS error, but the error won't be resolved as talos-ccm isn't running. 😄 )
Environment
The text was updated successfully, but these errors were encountered: