Documentation: missing instruction on how to generate cloud-controller-manager manifests ready to use about cloud-provider-gcp HOT 9 CLOSED

Thanks @BenTheElder. Teaches me to stop reading early. The CCM binary/image is built by bazel. However the manifest template can be found at https://github.com/kubernetes/cloud-provider-gcp/blob/master/cluster/gce/manifests/cloud-controller-manager.manifest. The template is then expanded by the function start-cloud-controller-manager at https://github.com/kubernetes/cloud-provider-gcp/blob/master/cluster/gce/gci/configure-helper.sh#L2205.

from cloud-provider-gcp.

Got it. My assumption that it was a bazel process in the build was wrong (totally newbie at bazel). It's just templating used internaly right ?

So I guess i should rephrase my question

I have a vanilla k3s cluster runing on GCP nodes. How to generate / find manifests to deploy the cloud provider in the cluster (mainly to have LB svc support) ? Same way i did this on aws: https://github.com/kubernetes/cloud-provider-aws/tree/master/manifests/base

from cloud-provider-gcp.

/cc @jiahuif @BenTheElder

from cloud-provider-gcp.

@cheftako is this even done with bazel? You mean the pod spec for running it? Pretty sure that's done with a bunch of bash in the cluster/ dir. If you mean manifests as in multi-arch images then https://github.com/kubernetes/cloud-provider-gcp#publishing-gcp-controller-manager-image

from cloud-provider-gcp.

The comment just above #232 (comment) contains the template of the manifest for deployment, which is templated by the shell code linked above. That script is part of a larger script that brings up test clusters for development + CI.

Bazel is used to build the docker images currently, but not for the manifest templating.

from cloud-provider-gcp.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from cloud-provider-gcp.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from cloud-provider-gcp.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

from cloud-provider-gcp.

@k8s-triage-robot: Closing this issue.

from cloud-provider-gcp.