mirror of https://github.com/kubernetes/kops.git
				
				
				
			Merge pull request #3908 from KashifSaadat/canal-calico-upgrade-steps
Automatic merge from submit-queue. Updated 1.8 release notes to cover Canal manual upgrade steps.
This commit is contained in:
		
						commit
						ee6762dbbe
					
				|  | @ -14,6 +14,13 @@ or `--networking flannel-udp` can be specified to explicitly choose a backend mo | |||
|   See the *Changes to k8s-policy* section in the | ||||
|   [Calico release notes](https://github.com/projectcalico/calico/releases/tag/v2.4.0) | ||||
|   for help. | ||||
| * Due to `ThirdPartyResources` becoming fully deprecated in Kubernetes v1.8 (replaced by `CustomResourceDefinitions`), existing Canal users upgrading their Clusters to Kubernetes v1.8 must follow the below TPR->CRD migration steps: | ||||
|   1. Run: `kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v2.6.2/upgrade/v2.5/manifests/upgrade-job.yaml` | ||||
|   2. Retrieve the pod name from describing the job: `kubectl describe job/calico-upgrade-v2.5` | ||||
|   3. Validate the last log line from the pod reports that it completed successfully: `kubectl logs calico-upgrade-v2.5-<random-id>` | ||||
|   4. Update the `KubernetesVersion` within your ClusterSpec to v1.8 (or above), performing an update & rolling-update to all nodes (will involve downtime) | ||||
|   5. Confirm cluster is back up and all canal pods are running successfully: `kops validate cluster` (this may take a few minutes for the cluster to fully validate) | ||||
|   6. Delete the upgrade job as it is no longer required: `kubectl delete job calico-upgrade-v2.5` (you can also safely delete the `clusterrole`, `clusterrolebinding` and `serviceaccount` resources that were created by the above manifest file) | ||||
| 
 | ||||
| # Full changelist | ||||
| 
 | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue