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
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rbjorklin
commented
Aug 19, 2017
rbjorklin
commented
- 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
This was referenced Aug 19, 2017
Open
|
I'm glad to see the whole guide updated. @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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.