kubernetes/cmd/cloud-controller-manager
Patrick Ohly 7d064812bb kube-controller-manager: finish conversion to contextual logging
This removes all exceptions and fixes the remaining unconverted log calls.
2023-07-12 14:57:29 +02:00
..
.import-restrictions kube-controller-manager: finish conversion to contextual logging 2023-07-12 14:57:29 +02: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 use klog.InfoS instead of klog.V(0),Info 2023-03-07 15:50:01 +08:00
OWNERS OWNERS cleanup - Jan 2021 Week 1 2022-01-10 08:14:29 -05:00
providers.go Remove AWS legacy cloud provider + EBS in-tree storage plugin 2023-03-06 14:01:15 +00: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.