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

Merge pull request #14221 from olemarkus/docs-fixes 

Some minor docs fixes
This commit is contained in:
Kubernetes Prow Robot 2022-09-01 13:35:29 -07:00 committed by GitHub
parent 3b5dccdf5e 82c2cdc07c
commit ad0e720801
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/cluster_spec.md
View File

@ -1506,6 +1506,8 @@ spec:
{{ kops_feature_table(kops_added_default='1.21') }}
**Warning**: Enabling the following configuration on an existing cluster can be disruptive due to the control plane provisioning tokens with different issuers. The symptom is that Pods are unable to authenticate to the Kubernetes API. To resolve this, delete Service Account token secrets that exists in the cluster and kill all pods unable to authenticate.
kOps can publish the Kubernetes service account token issuer and configure AWS to trust it
to authenticate Kubernetes service accounts:

2
docs/operations/etcd_backup_restore_encryption.md
View File

@ -76,7 +76,7 @@ kubectl get endpoints/kubernetes -o yaml
If you see more address than masters, you will need to remove it manually inside the etcd cluster.
See [etcd administation](etcd-administration.md) how to obtain access to the etcd cluster.
See [etcd administation](/operations/etcd_administration) how to obtain access to the etcd cluster.
Once you have a working etcd client, run the following:
```