docs: Add guides for calico cleanup after upgrading to v3.5 #1137
Conversation
CecileRobertMichon
changed the title
| @@ -170,6 +170,16 @@ Per default Calico still allows all communication within the cluster. Using Kube | |||
| - [NetworkPolicy Example Walkthrough](https://kubernetes.io/docs/getting-started-guides/network-policy/walkthrough/) | |||
| - [Calico Kubernetes](https://github.com/Azure/aks-engine/blob/master/examples/networkpolicy) | |||
|
|
|||
| ### Calico 3.3 cleanup after upgrading to 3.5 | |||
There was a problem hiding this comment.
would https://github.com/Azure/aks-engine/blob/master/examples/networkpolicy/README.md be a better place to put this?
There was a problem hiding this comment.
There was a problem hiding this comment.
Ha, I already suggested to Pengfei to move to docs/
But generally open to whatever makes the most sense.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: feiskyer If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| https://github.com/Azure/aks-engine/raw/master/docs/topics/calico-3.3.1-cleanup-after-upgrade.yaml | ||
|
|
||
| There are some placeholder tokens in the above `yaml` file, so please reconcile those with the actual values in your cluster. Look for these placeholder strings in the spec, then compare with the running spec of the comparable pre-3.5 resource in your cluster, and modify the cleanup spec accordingly: | ||
|
|
There was a problem hiding this comment.
Since the manifest is only used for cleanup, those changes are actually not required.
Reason for Change:
Add guides for calico cleanup after upgrading to v3.5.
Issue Fixed:
Fixes #908.
Requirements:
Notes: