How to Prioritize Startup of Wavefront Node Collector Pods in AKS

Products

• Insights

Issue/Introduction

To prioritize the startup of Wavefront node collector pods in Azure Kubernetes Service (AKS), you can use Kubernetes Priority and Preemption feature along with PriorityClass. This guide will walk you through the steps to set it up.
( Please adjust the YAML file names and content to match your environment and deployment configurations. )

Step 1: Create a PriorityClass

Create a PriorityClass YAML file (e.g., `wavefront-node-collector-priority.yaml`) that assigns a higher priority to the Wavefront node collector pods:

apiVersion: scheduling.k8s.io/v1
kind: PriorityClass
metadata:
name: wavefront-node-collector-priority
value: 1000

In this example, the PriorityClass "wavefront-node-collector-priority" is assigned a priority value of 1000, which is higher than the default priority (0).

Step 2: Assign PriorityClass to Pod

Modify the deployment YAML file for the Wavefront node collector pods to specify the PriorityClass:

apiVersion: apps/v1
kind: Deployment
metadata:
name: wavefront-node-collector
spec:
template:
spec:
priorityClassName: wavefront-node-collector-priority

In the spec section of the deployment YAML, add the `priorityClassName` field and set it to the name of the PriorityClass you created.

Step 3: Apply Changes

Apply the changes by deploying the PriorityClass and updating the Wavefront node collector deployment YAML:

kubectl apply -f wavefront-node-collector-priority.yaml
kubectl apply -f wavefront-node-collector-deployment.yaml

Step 4: Monitor and Verify

Monitor the startup of Wavefront node collector pods and verify that they are prioritized over other pods in AKS. You can use Kubernetes dashboard, `kubectl` commands, or Wavefront itself for monitoring.

By assigning a higher priority to the Wavefront node collector pods using PriorityClass, Kubernetes will prioritize their startup over other pods with lower priority. Adjust the priority value as needed based on your specific requirements and environment.

 

Caution: While this is a suggested method to prioritize the startup of Wavefront node collector pods in Azure AKS, it's important to note that this function falls outside the VMware AOA product. Therefore, we caution that this is a suggested approach, and we cannot take full ownership of the solution..