00e4a599f6
All Kubernetes commands should show flags with hyphens in their help text even when the flag originally was defined with underscore. Converting a command to this style is not breaking its command line API because the old-style parameter with underscore is accepted as alias. The easiest solution to achieve this is to set normalization shortly before running the command in the new central cli.Run or the few places where that function isn't used yet. There may be some texts which depends on normalization at flag definition time, like the --logging-format usage warning. Those get generated assuming that hyphens will be used. |
||
|---|---|---|
| .. | ||
| .import-restrictions | ||
| main.go | ||
| nodeipamcontroller.go | ||
| OWNERS | ||
| providers.go | ||
| 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-managerin this repo. - Make specific cloud provider changes here.