Skip to content

Commit 8afb0e4

Browse files
committed
add steps to retrive SAN
1 parent 0d12684 commit 8afb0e4

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/operator-nexus/howto-kubernetes-cluster-connect.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,16 @@ Establish direct access to the cluster's CNI (Container Network Interface) from
120120

121121
Reach out to your network administrator to set up this direct connection to the cluster's CNI network.
122122
123+
### Retrieve the Subject Alternative Name (SAN) for the cluster
124+
125+
Run the following commands to retrieve the Subject Alternative Name (SAN) to be used in your SSL/TLS certificates. First, identify the Control plane node by listing all nodes as described in step 1 [here](### Access to cluster nodes via Azure Arc for Kubernetes). Set up a privileged pod to run on the cluster's control plane node and connect to it as described in [step 2](### Access to cluster nodes via Azure Arc for Kubernetes). This gives you access to the API server and its corresponding cert. You can now retrieve the cert using the following command:
126+
127+
```bash
128+
openssl x509 -in /etc/kubernetes/pki/apiserver.crt -text -noout
129+
```
130+
131+
You can now retrieve the the SAN from the X509v3 Subject Alternative Name parameter of the output.
132+
123133
## IP address of the cluster nodes
124134

125135
Before you can connect to the cluster nodes, you need to find the IP address of the nodes. The IP address of the nodes can be found using the Azure portal or the Azure CLI.

0 commit comments

Comments
 (0)