Commit Graph

5 Commits

Author SHA1 Message Date
Justin Santa Barbara 148a65e1ad Fix CNI CPU allocations
* Limit each CNI provider to 100m

* Remove CPU limits - they cause serious problems
(https://github.com/kubernetes/kubernetes/issues/51135), but this also
makes the CPU allocation less problematic.

* Bump versions and start introducing the `-kops.1` suffix preemptively.

* Upgrade flannel to 0.9.0 as it fixes a lot.
2017-11-13 01:28:40 -05:00
Murali Reddy 2c7d85f480 Remove beta annotation versions (deprectated in 1.8) of init containers and move init
container to spec section
2017-10-13 02:29:36 +05:30
Murali Reddy a43df55540 Certificate generated for kube-router has CN system:kube-router, so user
system:kube-router need to be given necessary RBAC permissions

Fixes #3463
2017-10-05 21:29:11 +05:30
Murali Reddy 9b8f74d569 remove --cluster-cidr from manifest.
Kube-router was using --cluster-cidr flag to get the subnet allocated
for pod CIDR's. But now kube-router has the ability internally to infer
the CIDR allocated for the pod's by getting the information from
kubernetes API server node spec's
2017-08-25 01:21:51 +05:30
Murali Reddy e872dbcb86 add support for kube-router as CNI networking provider
fixes #2606

Most part of the changes are similar to current supported CNI networking
provider. Kube-router also support IPVS bassed service proxy which can
be used as replacement for kube-proxy. So the manifest for kube-router
included with this patch enables kube-router to provide pod-to-pod
networking, IPVS based service proxy and ingress pod firewall.
2017-06-09 17:01:31 +05:30