kubernetes/cmd/cloud-controller-manager
Andrew Sy Kim 0a4f582c8b cloud-controller-manager: don't run cloud IPAM controller when cloud provider is not enabled
Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
2022-12-20 10:29:02 -05:00
..
.import-restrictions Introduce MultiCIDRRangeAllocator 2022-08-06 00:10:39 +00:00
main.go fix grammar 2021-11-13 23:23:04 +05:30
nodeipamcontroller.go cloud-controller-manager: don't run cloud IPAM controller when cloud provider is not enabled 2022-12-20 10:29:02 -05:00
OWNERS OWNERS cleanup - Jan 2021 Week 1 2022-01-10 08:14:29 -05:00
providers.go Remove references to openstack and cinder 2022-08-22 16:43:14 -04:00
README.md Separate example func and add README.md 2021-03-01 10:22:09 -08:00

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.