Need K8s configure on existing Azure Local Cluster and Arc Resource Bridge

Question

Need K8s configure on existing Azure Local Cluster and Arc Resource Bridge

Rasitha Mudugama Hewage 180

Hi Support,

I need to configure k8s on existing Azure Local cluster and Arc Resource Bridge and please send me step by step guideline to complete it.

Rasitha Mudugama Hewage 180 Reputation points

2025-12-18T12:45:42.9566667+00:00

Hi I receive following error.

Provisioning the AKSArc cluster. This operation might take a while...

APIServerNotOnline) Error: Failed to either reach kube-apiserver or control plane IP X.X.X.X:6443 of Kubernetes cluster
Ankit Yadav 8,800 Reputation points Microsoft External Staff Moderator

2025-12-18T20:29:13.1466667+00:00
Hey @Rasitha Mudugama Hewage

Thanks for sharing the error details, this error typically occurs when the AKS Arc control plane API server is not accessible.

Common Causes for This Error:

Network/Firewall Issues: Port 6443 blocked or network misconfiguration

Rule it out by checking:

From AKS HCI host / management VM:
Test-NetConnection <control-plane-IP> -Port 6443

you should see TcpTestSucceeded = True in working case.

Also, ensure no firewall blocks on:

Azure Stack HCI host firewall

Physical firewall between hosts and control plane network

Verify the vSwitch/VLAN used for AKS allows traffic between:

AKS nodes

Control plane IP range

Resource Bridge VM

If 6443 connects successfully from multiple nodes, networking is not the issue.

IP Address Conflict: Control plane IP already in use

Rule it out by checking:

Ping the intended control plane IP before deployment:
Test-Connection <control-plane-IP> -Count 2

Any reply = IP conflict

Check ARP table (for 2nd validation):
arp -a | findstr <control-plane-IP>

Verify IP is outside:

DHCP scopes

Static server IP ranges

Load balancer IPs

If the IP never responds and doesn’t appear in ARP, conflict is unlikely.

Resource Bridge issues (Arc Resource Bridge not healthy)

Rule it out by checking:

Resource Bridge VM exists and is running:
Get-VM | Where-Object Name -like "*bridge*"

Resource Bridge pods are healthy:
kubectl get pods -n azure-arc

You should see pods in Running state

No crash loops:
kubectl get pods -n azure-arc | findstr Crash

If VM is running and pods are healthy, Resource Bridge is not the blocker.

4. DNS Resolution: Hostname resolution failures
Rule it out by checking:

Resolve the API server hostname:
Resolve-DnsName <api-server-fqdn>

Wokring case: Returns correct IP

From AKS host and Resource Bridge VM:
nslookup <api-server-fqdn>

Confirm DNS servers configured in AKS network settings are:

Reachable

Correct for that subnet

If hostname resolves consistently from all components, DNS is ruled out.

Kindly validate these common errors and let us know the results in Private Message.
Rasitha Mudugama Hewage 180 Reputation points

2025-12-19T08:12:36.27+00:00

Hi , Iam receiving following error now.
Ankit Yadav 8,800 Reputation points Microsoft External Staff Moderator

2025-12-19T18:07:42.2966667+00:00

The new error is related to AKSAddonNotReady and is being discussed over new Q&A thread: https://learn.microsoft.com/en-us/answers/questions/5671724/timed-out-waiting-for-the-operation-to-complete-de

Answer accepted by question author

0 additional answers

Your answer

Rasitha Mudugama Hewage 180 Reputation points

2025-12-18T12:45:42.9566667+00:00

Hi I receive following error.

Provisioning the AKSArc cluster. This operation might take a while...

APIServerNotOnline) Error: Failed to either reach kube-apiserver or control plane IP X.X.X.X:6443 of Kubernetes cluster
Rasitha Mudugama Hewage 180 Reputation points

2025-12-19T08:12:36.27+00:00

Hi , Iam receiving following error now.
Ankit Yadav 8,800 Reputation points Microsoft External Staff Moderator

2025-12-19T18:07:42.2966667+00:00

The new error is related to AKSAddonNotReady and is being discussed over new Q&A thread: https://learn.microsoft.com/en-us/answers/questions/5671724/timed-out-waiting-for-the-operation-to-complete-de

Answer 1

Hey @Rasitha Mudugama Hewage ,

It sounds like you're looking to set up Kubernetes on your existing Azure Local cluster and connect it with the Arc Resource Bridge. Here’s a step-by-step guideline to help you get started:

Step-by-Step Guide to Configure Kubernetes on Azure Local with Arc Resource Bridge

Prerequisites:
- Ensure you have an Azure account with an active subscription.
- Your Azure Local cluster should be set up and running.
- Make sure you have the latest Azure CLI version installed on your machine.
Install the AKS Arc Support Module:
- Before you start, it's a good idea to install and run the AKS Arc support module to diagnose any potential issues that might arise during your configuration.
Create the API Server and Connect to Your AKS Cluster:
- You can use the Azure CLI to connect to your AKS cluster. Run the following:
```
     az connectedk8s proxy --name <YourAKSClusterName> --resource-group <YourResourceGroup> --file .\aks-arc-kube-config
```
- This command will create a proxy connection to your Kubernetes cluster. Keep this terminal open while you verify your connection in another terminal.
Verify the Connection to Your Cluster:
- In a new terminal, execute the following command to check your cluster nodes:
```
     kubectl get node -A --kubeconfig .\aks-arc-kube-config
```
- Ensure that the nodes appear and their statuses are listed as Ready.
Deploying Applications:
- Once connected, you can start deploying applications on your AKS cluster. You may want to create Kubernetes deployment YAML files or use Helm for managing your applications.
Set Up Ingress:
- For managing external access to your services, consider setting up an ingress controller. Refer to Ingress for AKS for setup instructions.
Monitor and Troubleshoot:
- If you encounter issues, consult the troubleshooting guide for common issues with AKS on Azure Local.

Useful Links for References:

Feel free to ask if you have any questions or if there's anything else you need help with!

Share via

Need K8s configure on existing Azure Local Cluster and Arc Resource Bridge

0 additional answers

Your answer