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

Merge pull request #11154 from justinsb/release_notes_around_kubeconfig_export 

Clarify release notes around exporting kubeconfig
This commit is contained in:
Kubernetes Prow Robot 2021-03-27 04:38:43 -07:00 committed by GitHub
parent ffc8a851bf 1a9dd01811
commit 2dba967b0e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/releases/1.19-NOTES.md
View File

@ -8,7 +8,7 @@
## Changes to kubernetes config export
kOps will no longer automatically export the kubernetes config on `kops update cluster`. In order to export the config on cluster update, you need to either add the `--user <user>` to reference an existing user, or `--admin` to export the cluster admin user. If neither flag is passed, the kubernetes config will not be modified. This makes it easier to reuse user definitions across clusters should you, for example, use OIDC for authentication.
kOps will no longer automatically export user credentials on `kops update cluster`. In order to export user credentials on cluster update, you need to either add the `--user <user>` to reference an existing user block in kubeconfig, or `--admin` to export the cluster admin user. If neither flag is passed, the kubernetes user config will not be modified. This makes it easier to reuse user definitions across clusters should you, for example, use OIDC for authentication.
Similarly, `kops export kubecfg` will also require passing either the `--admin` or `--user` flag if the context does not already exist.