[BUG] Creating a WorkloadSpread with a patch for the priorityClassName fails

[ludat]

What happened:

Creating a WorloadSpread that patches .spec.priorityClassName for a deployment fails on the k8s api with:

Error creating: pods "*******-prod-app-79644979d8-" is forbidden: the integer value of priority (0) must not be provided in pod spec; priority admission controller computed 1000000000 from the given PriorityClass name

What you expected to happen:

The pods are distributed according to the WorkloadSpread

How to reproduce it (as minimally and precisely as possible):

I don't have a minimal example yet but I'll try to get it next week

Anything else we need to know?:

Not sure if it's relevant but I'm on GKE

Environment:

• Kruise version: v1.6.3
• Kubernetes version (use kubectl version): v1.28.7-gke.1026000
• Install details (e.g. helm install args):
• Others:

[furykerry]

@ludat the problem may be related to the order of multiple webhooks and admission plugins. Can you patch spec.priority along with with priorityClassName?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ludat]

@furykerry I'll try to do this this week, will report back