istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

auth: do not remove crd in upgrade note (#7406)

This commit is contained in:
Yangmin Zhu 2020-05-27 06:39:58 -07:00 committed by GitHub
parent 0734eba8f4
commit 3cca5180d5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
content/en/news/releases/1.6.x/announcing-1.6/upgrade-notes/index.md
View File

@ -87,17 +87,6 @@ $ kubectl get servicerolebindings.rbac.istio.io --all-namespaces
If there are any `v1alpha1` security policies in your clusters, migrate to the new APIs before upgrading.
To ensure that `v1alpha1` security policies aren't applied in the future, delete the Custom Resource Definitions (CRDs) using the `v1alpha1` security policy APIs with the following commands:
{{< text bash >}}
$ kubectl delete crd policies.authentication.istio.io
$ kubectl delete crd meshpolicies.authentication.istio.io
$ kubectl delete crd rbacconfigs.rbac.istio.io
$ kubectl delete crd clusterrbacconfigs.rbac.istio.io
$ kubectl delete crd serviceroles.rbac.istio.io
$ kubectl delete crd servicerolebindings.rbac.istio.io
{{< /text >}}
## Istio configuration during installation
Past Istio releases deployed configuration objects during installation. The presence of those objects caused the following issues: