Assign pod priority

Pod priority can be used to indicate the significance of a pod compared to other pods. Assigning priority to pods is important to ensure that high-priority pods are not preempted and can use required resources. For example, if a pod cannot be scheduled, the scheduler will attempt to free up resources by evicting lower-priority pods. When enough resources are available, the higher-priority pods can be scheduled.

To assign priority for pods:

1. Add a PriorityClass. This example shows a PriorityClass with a value of 1 million:

   Copy

   apiVersion: scheduling.k8s.io/v1
   kind: PriorityClass
   metadata:
     name: high-priority
   value: 1000000
   globalDefault: false
   description: "This high priority class should be used for MarkLogic pods only."
   
   

2. For Helm Charts, set priorityClassName to one of the added PriorityClassNames through the values.yaml file or by using --set flag while installing the chart.

3. For Operator, set priorityClassName to one of the added PriorityClassNames through the sample.yaml file.