kubernetes/cmd/cloud-controller-manager
Davanum Srinivas 7f9a0ef5d2
Fixes from review by Jan Šafránek/Andrew/Michael
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
2024-05-03 15:11:36 -04:00
..
.import-restrictions Allow specifying ExternalTrafficPolicy for ClusterIP Services with ExternalIPs 2023-08-30 23:56:47 +08:00
main.go use controller names for CLI FlagSets to show the names in help 2023-06-19 15:01:01 +02:00
nodeipamcontroller.go remove ClusterCIDR 2023-10-14 19:06:22 +00:00
OWNERS OWNERS cleanup - Jan 2021 Week 1 2022-01-10 08:14:29 -05:00
providers.go Fixes from review by Jan Šafránek/Andrew/Michael 2024-05-03 15:11:36 -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.