Context for the Shared Cluster

This documentation describes the legacy CDK implementation, which will be deprecated in an upcoming release. We strongly recommend that you transition to the current CDK implementation as soon as possible.

Kubernetes uses contexts to access Kubernetes clusters. Before you can access the shared cluster, you must create a context on your local computer if it’s not already present.

To create a context for the shared cluster:

Run the kubectx command and review the output. The current Kubernetes context is highlighted:
- If the current context references the shared cluster, there is nothing further to do. Proceed to Namespace.
- If the context of the shared cluster is present in the kubectx command output, set the context as follows:
  $ kubectx my-context Switched to context "my-context".
  After you have set the context, proceed to Namespace.
- If the context of the shared cluster is not present in the kubectx command output, continue to the next step.
Configure the Azure CLI to use your Microsoft Azure. Run the following command:
```
$ az login
```
A browser window prompts you to log in to Azure. Log in using your Microsoft account.

A second screen should appear with the message, "You have logged into Microsoft Azure!"
Return to the terminal window and run the following command. Use the resource group, cluster name, and subscription ID you obtained from your cluster administrator:
```
$ az aks get-credentials \
 --resource-group my-fr-resource-group \
 --name my-fr-cluster \
 --subscription your subscription ID \
 --overwrite-existing
```
Run the kubectx command again and verify that the context for your Kubernetes cluster is now the current context.

ForgeOps

Context for the Shared Cluster

Next Step