k3s/contrib
Justin Santa Barbara b754393630 kube-controller-manager: Add configure-cloud-routes option
This allows kube-controller-manager to allocate CIDRs to nodes (with
allocate-node-cidrs=true), but will not try to configure them on the
cloud provider, even if the cloud provider supports Routes.

The default is configure-cloud-routes=true, and it will only try to
configure routes if allocate-node-cidrs is also configured, so the
default behaviour is unchanged.

This is useful because on AWS the cloud provider configures routes by
setting up VPC routing table entries, but there is a limit of 50
entries.  So setting configure-cloud-routes on AWS would allow us to
continue to allocate node CIDRs as today, but replace the VPC
route-table mechanism with something not limited to 50 nodes.

We can't just turn off the cloud-provider entirely because it also
controls other things - node discovery, load balancer creation etc.

Fix #25602
2016-05-27 09:42:20 -04:00
..
completions Merge pull request #20672 from brendandburns/dump 2016-05-24 14:24:17 -07:00
mesos kube-controller-manager: Add configure-cloud-routes option 2016-05-27 09:42:20 -04:00
README.md add readme to redirect people to new repo 2015-08-13 17:53:12 -07:00

README.md

Kubernetes Contrib is moving!

Checkout https://github.com/kubernetes/contrib for anything that is missing here!

Analytics