Skip to content

Commit 765bde7

Browse files
committed
add steps to retrive SAN
1 parent 8afb0e4 commit 765bde7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: dramasamy
55
ms.author: dramasamy
66
ms.service: azure-operator-nexus
77
ms.topic: how-to
8-
ms.date: 08/17/2023
8+
ms.date: 01/21/2025
99
ms.custom: template-how-to-pattern, devx-track-azurecli
1010
---
1111

@@ -122,7 +122,7 @@ Reach out to your network administrator to set up this direct connection to the
122122
123123
### Retrieve the Subject Alternative Name (SAN) for the cluster
124124
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:
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:
126126

127127
```bash
128128
openssl x509 -in /etc/kubernetes/pki/apiserver.crt -text -noout

0 commit comments

Comments
 (0)