Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins pod priority cannot be set with priorityClassName parameter #966

Open
SohamChakraborty opened this issue Dec 11, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@SohamChakraborty
Copy link

SohamChakraborty commented Dec 11, 2023

Pod priority is not changing

Hi,

We are trying to give Jenkins pods a higher priority than 0.

For that we tried to set priorityClassName to an already existing priorityclass. After then we tried to upgrade the release with helm upgrade. But the change doesn't get reflected.

Any idea whether we are doing something wrong here? Has it worked for someone else?

controller:
  componentName: "jenkins-controller"
  image: "jenkins/jenkins"
  tag: "lts-jdk11"
  imagePullPolicy: "Always"
  ...
  podAnnotations:
    cluster-autoscaler.kubernetes.io/safe-to-evict: "false"
  priorityClassName: "pre-existing-priorityclass"

Version of Helm and Kubernetes

- Helm: v3.11.3
- Kubernetes: v1.23.5

Chart version

jenkins-4.1.13

What happened?

1. Change the parameter of `priorityClassName` in `values.yaml`.
2. Run `helm upgrade`.
3. The change is not being reflected.
...

What you expected to happen?

The pod priority should change

How to reproduce it

No response

Anything else we need to know?

No response

@SohamChakraborty SohamChakraborty added the bug Something isn't working label Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant