How to Prioritize Startup of Wavefront Node Collector Pods in AKS

Products

• Insights
• Observability
• DX OpenExplore

Issue/Introduction

Prioritizing the startup of Wavefront node collector pods in Azure Kubernetes Service (AKS) ensures critical monitoring components initialize before other workloads. This is achieved using the Kubernetes Priority and Preemption feature along with a defined PriorityClass.

DX OpenExplore(OE) is not responsible for the start up order of pods in a Kubernetes cluster. The below is provided as a suggestion only and should be thoroughly tested and validated before applying to any production environment.

Resolution

This guide will walk you through the steps to set it up.

• Remember to 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) to assign higher priority:

yaml

 

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

The value of 1000 ensures these pods are scheduled before default-priority pods (value 0).

Step 2: Assign PriorityClass to Pod Modify the deployment YAML for the Wavefront node collector:

yaml

 

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

Step 3: Apply Changes Review these commands before running them:

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

 

Step 4: Monitor and Verify Verify pod startup order using the Kubernetes dashboard or kubectl commands.

Assigning a higher priority value ensures Kubernetes prioritizes these pods during scheduling and preemption.

Additional Information

• Deploy the Monitoring Agents with the Observability for Kubernetes Operator
• Kubernetes FAQ
• Kubernetes Troubleshooting

For further assistance or support with this topic, please open a support ticket through our Support @ Broadcom portal.