kubernetes/cmd/cloud-controller-manager
Khaled Henidak (Kal) a53e2eaeab
move IPv6DualStack feature to stable. (#104691)
* kube-proxy

* endpoints controller

* app: kube-controller-manager

* app: cloud-controller-manager

* kubelet

* app: api-server

* node utils + registry/strategy

* api: validation (comment removal)

* api:pod strategy (util pkg)

* api: docs

* core: integration testing

* kubeadm: change feature gate to GA

* service registry and rest stack

* move feature to GA

* generated
2021-09-24 16:30:22 -07:00
..
.import-restrictions Add demonstration of wiring nodeIPAMController config object 2021-03-01 10:21:52 -08:00
main.go Allow custom client names to be used for cloud controllers 2021-08-24 00:51:24 +00:00
nodeipamcontroller.go move IPv6DualStack feature to stable. (#104691) 2021-09-24 16:30:22 -07:00
OWNERS Adding cheftako to CCM owners. 2020-09-17 14:52:53 -07:00
providers.go generated: Run hack/update-gofmt.sh 2021-08-24 15:47:49 -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.