scratch.md: kubeconfig should not embed the CA cert
This commit is contained in:
parent
3e55a5ba5a
commit
5b91603d69
|
|
@ -280,7 +280,7 @@ users:
|
|||
clusters:
|
||||
- name: local
|
||||
cluster:
|
||||
certificate-authority-data: ${CA_CERT_BASE64_ENCODED}
|
||||
certificate-authority: /srv/kubernetes/ca.crt
|
||||
contexts:
|
||||
- context:
|
||||
cluster: local
|
||||
|
|
@ -289,10 +289,6 @@ contexts:
|
|||
current-context: service-account-context
|
||||
```
|
||||
|
||||
Where CA_CERT_BASE64_ENCODED can be generated like `< ca.crt base64
|
||||
-w0`. Alternatively you can refer to a file (e.g. `certificate-authority:
|
||||
/etc/kubernetes/ca.crt`).
|
||||
|
||||
Put the kubeconfig(s) on every node. The examples later in this
|
||||
guide assume that there are kubeconfigs in `/var/lib/kube-proxy/kubeconfig` and
|
||||
`/var/lib/kubelet/kubeconfig`.
|
||||
|
|
|
|||
Loading…
Reference in New Issue