Skip to content

Add nodeselector, affinity, and toleration configuration options to the helm chart - #311

Open
cooksec wants to merge 1 commit into
permitio:mainfrom
cooksec:main
Open

cooksec wants to merge 1 commit into
permitio:mainfrom
cooksec:main

Conversation

@cooksec

@cooksec cooksec commented May 5, 2026

Copy link
Copy Markdown

This change allows users to optionally define nodeselector, affinity, and/or toleration options to their deployments via helm values. This allows users to better distribute their PDP deployments across their node pools. The default values for each are empty, ensuring this change does not affect existing deployments.

Closes #310

…he helm chart

This change allows users to optionally define nodeselector, affinity, and/or toleration options to their deployments via helm values.
This allows users to better distribute their PDP deployments across their node pools.
The default values for each are empty, ensuring this change does not affect existing deployments.
@zeevmoney

Copy link
Copy Markdown
Member

Thanks for this, @cooksec, and sorry for the slow review. Your change is included in #388 with you credited as co-author, plus the chart version bump to 0.0.7 so it actually publishes. We checked it with helm template and on a test cluster: with the new values, the pod schedules onto a tainted node and becomes Ready, and the default render is unchanged. We'll close this PR once #388 merges; #310 closes with it.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature request: allow configuration of pod affinity properties

2 participants