Table of Contents

1. Challenge

   Connect a Kubernetes Cluster to Azure Arc

   1. Connect the single node k3s cluster running on LinuxVM to Azure Arc using the Azure CLI on LinuxVM.

      Note: k3s has been installed on the virtual machine, and kubectl installed by k3s will automatically use the kubeconfig file located at /etc/rancher/k3s/k3s.yaml.

      Note: By default, only the root user has access to read the kubeconfig file. You can grant the cloud_user account access to the kubeconfig file using the commands listed below:

      sudo groupadd k3s
      sudo usermod -a -G k3s cloud_user
      sudo chown root:k3s /etc/rancher/k3s/k3s.yaml
      sudo chmod 740 /etc/rancher/k3s/k3s.yaml
      

   2. Log out and back in again for your group membership to be updated.

      exit
      ssh cloud_user@<LinuxVM Public IP>
      

2. Challenge

   Grant Entra Accounts Cluster Privileges

   1. Grant your Entra account cluster-admin privileges using the Azure CLI and kubectl on LinuxVM.

      Note: You can use the below command to retrieve your User ID:

      USER_ID=$(az ad signed-in-user show --query userPrincipalName -o tsv)
      

3. Challenge

   Use Cluster Connect to Securely Connect to an Azure Arc-enabled Kubernetes Cluster

   1. Connect to WinVM using Remote Desktop, then use the Azure CLI to set up Cluster Connect, and connect to the cluster.

   Note: In a corporate environment where your Windows PC is domain-joined, you may need to prefix the username with .\ when connecting via a remote desktop client (e.g., .\cloud_user).