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

Upgraded Kubernetes to 1.7.3 and Calico to 2.4.1 #902

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

rbjorklin
Copy link

  • Tested & working with CoreOS Alpha 1506.0.0
  • Upgraded Kubernetes from 1.5.4 to 1.7.3
  • Upgraded Calico from 0.23.0 to 2.4.1
  • Upgraded kube-dns from 1.9 to 1.14.4
  • Upgraded dns-autoscaler from 1.0.0 to 1.1.2
  • Upgraded heapster from 1.2.0 to 1.4.1
  • Upgraded kube-dashboard from 1.5.0 to 1.6.3
  • Changed from using etcd2 to etcd version 3
  • Changed Calico to the default network solution
  • Changed POD_NETWORK from 10.2.0.0/16 to 192.168.0.0/16 as Calico does not respect CALICO_IPV4POOL_CIDR
  • Changed Vagrant memory limits for the controller, increased to 2Gb
  • Removed Kubelet usage of deprecated flag --api-servers
  • Removed Kubelet usage of deprecated flag --register-schedulable
  • Added a kubeconfig to make up for the removed flags above
  • Added possibility to modify how many cpu cores Vagrant assigns the hosts

* Upgraded Kubernetes from 1.5.4 to 1.7.3
* Upgraded Calico from 0.23.0 to 2.4.1
* Upgraded kube-dns from 1.9 to 1.14.4
* Upgraded dns-autoscaler from 1.0.0 to 1.1.2
* Upgraded heapster from 1.2.0 to 1.4.1
* Upgraded kube-dashboard from 1.5.0 to 1.6.3
* Changed from using etcd2 to etcd version 3
* Changed Calico to the default network solution
* Changed POD_NETWORK from 10.2.0.0/16 to 192.168.0.0/16 as Calico does not respect CALICO_IPV4POOL_CIDR
* Changed Vagrant memory limits for the controller, increased to 2Gb
* Removed Kubelet usage of deprecated flag --api-servers
* Removed Kubelet usage of deprecated flag --register-schedulable
* Added a kubeconfig to make up for the removed flags above
* Added possibility to modify how many cpu cores Vagrant assigns the hosts
@tmjd
Copy link

tmjd commented Aug 23, 2017

I'm glad to see the whole guide updated.
Partially addresses #899

@rbjorklin Were you going to revert the change to the CIDR. We talked on the CalicoUsers slack and I think you understand CALICO_IPV4POOL_CIDR better now, do you still believe it is not respected?

* Upgraded Kubernetes from 1.7.3 to 1.7.4
* Upgraded Calico from 2.4.1 to 2.5.0
* Reverted configuration change for POD_NETWORK as my understanding of
  how Calico treats CALICO_IPV4POOL_CIDR was incorrect.
  CALICO_IPV4POOL_CIDR is used to create an initial pool and cannot
  later be changed and used as a way to assign a new pool without first
  removing the existing pool(s). Thanks @tmjd for clarifying this!
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants