Skip to content
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.

switch to 172.20.0.0/14 for networking #108

Closed
wants to merge 2 commits into from

Conversation

dysinger
Copy link

10.0.0.0/14 is really really popular for folks to already have in their infrastructure. If one wanted to vpc peer to the kubernetes cluster, it would be difficult with 10.0.0.0/14. 172.20.0.0/14 is probably less popular & more likely to just work.

Creating this patch shows that we need a way to have these network IP addresses & CIDRs as cluster.yaml settings & not hard coded into go & misc files. I will make sure there's an issue for this concern.

@dysinger
Copy link
Author

@silas
Copy link
Contributor

silas commented Oct 21, 2015

+1

Although longer term we should enable the AWS cloudprovider routes feature (https://github.com/kubernetes/kubernetes/blob/071d21257fdfd439a9286fffbd5972c85643cd49/pkg/cloudprovider/providers/aws/aws_routes.go) and make the subnets fully configurable.

* master:
  docs: fix kubelet arguments
  multi-node/aws: increase default volume size
  [multi-node/aws docs] update s3 artifact URL docs to recognize new s3 endpoint format
  *: bump to hyperkube v1.0.7
  ssl: generate admin cert for single-node install
  Documentation: kubernetes-on-aws
  MAINTAINERS: add Silas
  ssl: move ssl artifact gen scripts to new common lib location, use them in single node Vagrantfile
  ssl: Provision worker certificates with SANS for the worker's IP address. Consolidate init-ssl logic.
  Documentation/deploy-master: Explain register-node=0
  Documentation/configure-kubectl: s/vagrant/default/
  kubernetes-networking.md: fixed broken link
  multi-node/aws: Use the correct AWS role when creating workers.
  docs: networking and baremetal install
  flannel: use vxlan backend
  Fixed Kubernetes docs
  documentation: s/describe/status/
@bcwaldon
Copy link
Contributor

I don't want to change the defaults until all fields are configurable. This needs to land after #190

@phemmer
Copy link
Contributor

phemmer commented Dec 15, 2015

I would not recommend changing the default address anyway. At least not until kubernetes properly supports it.
Right now the 10.0.0.0/8 subnet is hard-coded in some parts of kubernetes: https://github.com/kubernetes/kubernetes/blob/v1.1.2/pkg/kubelet/container_bridge.go#L127

@bcwaldon
Copy link
Contributor

We are going to make this configurable for folks that don't need to rely on the portions of Kubernetes hard-coded to 10.0.0.0/8: #190. Please interface with the upstream community to address the issues preventing us from using a range outside of 10.0.0.0/8 if you believe it is important.

@bcwaldon bcwaldon closed this Dec 21, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants