Skip to content

Exposing PodLabels, PodAnnotations, and Tolerations on Deployment#139

Draft
onelapahead wants to merge 4 commits into
arttor:mainfrom
onelapahead:pod-settings
Draft

Exposing PodLabels, PodAnnotations, and Tolerations on Deployment#139
onelapahead wants to merge 4 commits into
arttor:mainfrom
onelapahead:pod-settings

Conversation

@onelapahead

Copy link
Copy Markdown
Contributor

Meant to close #119 . Need to add podAnnotations support and do some more testing before considering this ready.

Believe bc tolerations is in the pod spec it works for more than just deployments. So will have consider adding the podLabels and podAnnotations support to daemonsets, etc. and moving it to a more common place.

Signed-off-by: hfuss <hayden.fuss@kaleido.io>
Signed-off-by: hfuss <hayden.fuss@kaleido.io>
Made-with: Cursor
Adds podAnnotations support for Deployment resources. Static annotations
from the source manifest are preserved, with a values-driven merge block
appended so users can inject additional annotations at install/upgrade
time without re-generating the chart.

Also seeds podAnnotations: {} in values.yaml by default, consistent with
the existing podLabels field.

Closes arttor#119

Made-with: Cursor
@onelapahead onelapahead force-pushed the pod-settings branch 2 times, most recently from d7462ac to 6fc4890 Compare April 29, 2026 17:57
Signed-off-by: hfuss <hayden.fuss@kaleido.io>
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.

Allow specifying custom labels and annotations from values.yaml

1 participant