go-sylixos/kubernetes-sylixos
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
dev-1.29-sylixos
kubernetes-sylixos/cmd/cloud-controller-manager
History
Antonio Ojea c2d473f0d4 remove ClusterCIDR 
KEP-2593 proposed to expand the existing node-ipam controller
to be configurable via a ClusterCIDR objects, however, there
were reasonable doubts on the SIG about the feature and after
several months of dicussions we decided to not move forward
with the KEP intree, hence, we are going to remove the existing
code, that is still in alpha.

https://groups.google.com/g/kubernetes-sig-network/c/nts1xEZ--gQ/m/2aTOUNFFAAAJ

Change-Id: Ieaf2007b0b23c296cde333247bfb672441fe6dfc
2023-10-14 19:06:22 +00: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 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

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

  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.