Skip to main content

nodelocaldns or node-local-dns Patching Example

This document covers a high level patching example for the nodelocaldns app.

Patching

Review the Releases page to check for breaking changes.

Please note that the nodelocaldns app is NOT deployed in SDS, so you will only need to patch it in CFT.

An example PR for upgrading the version in CFT.


Accessing the AKS Cluster

To run the verification commands below, you must first connect to the AKS cluster using kubectl.

1. Log in to Azure

```
az login
```

2. Retrieve the AKS cluster credentials

For example: az aks get-credentials --resource-group <RESOURCE_GROUP_NAME> --name <CLUSTER_NAME>

This command configures kubectl so it can communicate with the cluster.

A list of the respective clusters can be found here.

3. Verify connectivity

```
kubectl get nodes
```

If the command returns a list of nodes, you are successfully connected to the cluster.


Checks to see if upgrade worked correctly

After the patching PR is raised, approved, and merged:

1. Check that the node-local-dns pods are running

Run the following command to list the pods in the kube-system namespace: kubectl get pods -n kube-system

Identify the node-local-dns-XXXX pod from the list.

2. Describe the node-local-dns pod

Run: kubectl describe pod <pod-name> -n kube-system

Look for the Image field in the output to confirm the running version.

This page was last reviewed on 10 March 2026. It needs to be reviewed again on 10 March 2027 by the page owner platops-build-notices .
This page was set to be reviewed before 10 March 2027 by the page owner platops-build-notices. This might mean the content is out of date.