Google Git
Sign in
cos/third_party/kubernetes/refs/heads/release-R129/./cmd/cloud-controller-manager
tree: 3611ca71621750b597d07639b5e93c0ec27e7661 [path history] [tgz]
  1. .import-restrictions
  2. main.go
  3. nodeipamcontroller.go
  4. OWNERS
  5. providers.go
  6. README.md
cmd/cloud-controller-manager/README.md

cloud-controller-manager/example

This directory provides an example of how to leverage CCM extension mechanism.

Purpose

Begin with 1.20, all cloud providers should not copy over or vendor in k8s.io/kubernetes/cmd/cloud-controller-manager. Inside this directory, an example is included to demonstrate how to leverage CCM extension mechanism to add a controller. Please refer to k8s.io/cloud-provider/sample if you do not have the requirement of adding/deleting controllers in CCM.

Things you should NOT do

  1. Vendor in k8s.io/cmd/cloud-controller-manager.
  2. Directly modify anything under k8s.io/cmd/cloud-controller-manager in this repo.
  3. Make specific cloud provider changes here.