Files

Nick Turner a5b47f7dd0 Allow custom client names to be used for cloud controllers

* This allows a controller to use cloud provider managed RBAC
  when --use-service-account-credentials is set.
* Create ControllerInitFuncConstructor to pass to init funcs to avoid
  future function signature growth.
* Add comments for context around legacy naming of node controllers.
* Add example for setting client names from cloud controller manager.

2021-08-24 00:51:24 +00: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

Allow custom client names to be used for cloud controllers

2021-08-24 00:51:24 +00:00

OWNERS

Adding cheftako to CCM owners.

2020-09-17 14:52:53 -07:00

providers.go

Add providerless tags

2020-07-30 13:48:40 -04:00

README.md

Separate example func and add README.md

2021-03-01 10:22:09 -08:00

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

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