generate kube-apiserver server certificate
parent
f377d2ad74
commit
b6e493e463
2
ca.conf
2
ca.conf
|
@ -174,7 +174,7 @@ req_extensions = kube-api-server_req_extensions
|
|||
basicConstraints = CA:FALSE
|
||||
extendedKeyUsage = clientAuth, serverAuth
|
||||
keyUsage = critical, digitalSignature, keyEncipherment
|
||||
nsCertType = client
|
||||
nsCertType = client, server
|
||||
nsComment = "Kube API Server Certificate"
|
||||
subjectAltName = @kube-api-server_alt_names
|
||||
subjectKeyIdentifier = hash
|
||||
|
|
|
@ -179,7 +179,8 @@ At this point the Kubernetes control plane is up and running. Run the following
|
|||
Make a HTTP request for the Kubernetes version info:
|
||||
|
||||
```bash
|
||||
curl -k https://server.kubernetes.local:6443/version
|
||||
curl --cacert ca.crt \
|
||||
https://server.kubernetes.local:6443/version
|
||||
```
|
||||
|
||||
```text
|
||||
|
|
|
@ -11,7 +11,7 @@ Each kubeconfig requires a Kubernetes API Server to connect to.
|
|||
You should be able to ping `server.kubernetes.local` based on the `/etc/hosts` DNS entry from a previous lab.
|
||||
|
||||
```bash
|
||||
curl -k \
|
||||
curl --cacert ca.crt \
|
||||
https://server.kubernetes.local:6443/version
|
||||
```
|
||||
|
||||
|
|
Loading…
Reference in New Issue