Skip to content

Commit 9de5f95

Browse files
committed
add steps to retrive SAN
1 parent 765bde7 commit 9de5f95

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

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

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -120,15 +120,6 @@ 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.
132123
133124
## IP address of the cluster nodes
134125
@@ -193,6 +184,17 @@ To find the IP address of the VM for SSH, follow these steps:
193184

194185
:::image type="content" source="media/nexus-kubernetes/control-plane-network-attachment.png" lightbox="media/nexus-kubernetes/control-plane-network-attachment.png" alt-text="Screenshot of browsing Nexus Kubernetes cluster node networks.":::
195186

187+
## Retrieve the Subject Alternative Name (SAN) for the cluster
188+
189+
Run the following commands to retrieve the list of Subject Alternative Names (SAN) accepted by the Kubernetes API server certificate. First, access the control plane node either [using Azure Arc for servers](#access-to-cluster-nodes-via-azure-arc-for-servers) or using the [interactive shell using IP address](#create-an-interactive-shell-connection-to-a-node-using-the-ip-address). This gives you access to the certificate used by the API server. You can inspect the content of the certificate using the following command with sudo privileges:
190+
191+
```bash
192+
sudo openssl x509 -in /etc/kubernetes/pki/apiserver.crt -text -noout
193+
```
194+
195+
Each of the SANs is identified by the prefix "DNS:". Please only choose the SANs that follow the specified naming convention "<clusterName>-<resourceGroup>", as this is unique compared to other SANs like "kubernetes.default.svc.cluster.local".
196+
197+
196198
## Next steps
197199

198200
Try out the following articles to learn more about Azure Operator Nexus Kubernetes cluster.

0 commit comments

Comments
 (0)