Skip to content

Add pod scheduling capability (#76) - #77

Merged
EliMoshkovich merged 1 commit into
permitio:masterfrom
cdav:master
Apr 28, 2026
Merged

Add pod scheduling capability (#76)#77
EliMoshkovich merged 1 commit into
permitio:masterfrom
cdav:master

Conversation

@cdav

@cdav cdav commented Dec 5, 2025

Copy link
Copy Markdown
Contributor

Adds support for Kubernetes pod scheduling to OPAL server and client deployments.

@orweis

orweis commented Dec 6, 2025

Copy link
Copy Markdown
Contributor

Is this ready for review?

@luborpetr

Copy link
Copy Markdown

Hey there,
are you going to merge those changes anytime soon?
I would love to have those extra options. so I don't have to fork the official chart..
Thx..

@cdav

cdav commented Feb 6, 2026

Copy link
Copy Markdown
Contributor Author

@orweis yes this is ready for review

@JackOneil

Copy link
Copy Markdown

Hi,
@danyi1212 @omer9564 @zeevmoney
could you please look into this and if possible review / merge? Would really appreciate this, thanks.

@EliMoshkovich

Copy link
Copy Markdown
Contributor

Hi @cdav @JackOneil @luborpetr, thanks for this contribution! The code looks good.

One change needed before we merge: please add the default values to values.yaml under both server and client.

server:

...existing fields...

podLabels: {}
nodeSelector: {}
tolerations: []
affinity: {}

client:

...existing fields...

podLabels: {}
nodeSelector: {}
tolerations: []
affinity: {}

Right now these fields are only in values.schema.json, so they won't appear when users run helm show values.
Every other configurable field in this chart is listed in values.yaml, let's keep that consistent.

Once that's in, happy to merge!

@EliMoshkovich

Copy link
Copy Markdown
Contributor

Hi @cdav @JackOneil @luborpetr , thanks again for this contribution! We've decided to merge this PR as-is.
We've opened #78 to add the values.yaml defaults on top.
Appreciate your work on this!

@EliMoshkovich
EliMoshkovich merged commit 2213113 into permitio:master Apr 28, 2026
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.

5 participants