-
Notifications
You must be signed in to change notification settings - Fork 208
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
CAPG: Upstream CCM manifest doesn't work #666
Comments
This issue is currently awaiting triage. If the repository mantainers determine 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/test-infra repository. |
Please use:
and remove the env. |
/kind support |
Hi @mcbenjemaa , Thanks for the help. CCM pod is up now with these args
One more doubt, I see the cloud-controller-manager image being used is |
You may have to build the image while the release process is being revampled, there are instructions in the README. The /retitle CAPG: Upstream CCM manifest doesn't work I don't think the manifest is necessarily meant to work with CAPG, I would expect CAPG to handle deploying everything? Otherwise this may be in scope for #686 |
Self deployed CCM:
|
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 |
Something similar here, i'm trying to deploy the Cloud Controller Manager (CCM) and I'm encountering the following error:
I don't understand why CCM is adding the label zone as:
The correct zone should be
|
what do you mean by correct zone there? the instance url is that is the providerId, isn't it? |
The issue is that the Is there any way to make the CCM check every single zone? Maybe a multizone option or something similar? |
Solved!
where
|
Tried deploying CCM in a CAPG cluster and used the provided CCM manifest from (https://github.com/kubernetes/cloud-provider-gcp/blob/master/deploy/packages/default/manifest.yaml).
The CCM pod is stuck in
CrashLoopBack
with this error:The text was updated successfully, but these errors were encountered: