chore: staging->master (olake-worker v0.3.10, olake-helm v0.0.23)#170
Merged
Conversation
* feat(fusion): add podLabels and podAnnotations hooks (#151) The other components in this chart (olake-ui, olake-worker, temporal, postgresql, nfs-server, elasticsearch) all support `podLabels` and `podAnnotations` value blocks that get merged into `spec.template.metadata`. The Fusion deployment template was missing both — its pod-template metadata was hardcoded to the `app.kubernetes.io/*` labels and the config-checksum annotation, with no extension point. This matters for deployments running under K8s admission policies that require specific labels on pod templates (Gatekeeper, Kyverno, OPA constraints, etc.). Without a `podLabels` hook, operators either have to live with the policy warnings or carry parent-chart patches. Changes mirror the same pattern olake-ui/deployment.yaml already uses: template: metadata: labels: app.kubernetes.io/name: ... ... {{- with .Values.fusion.podLabels }} {{- toYaml . | nindent 8 }} {{- end }} annotations: checksum/fusion-config: ... {{- with .Values.fusion.podAnnotations }} {{- toYaml . | nindent 8 }} {{- end }} Defaults are `{}` in values.yaml so existing deployments render byte-identically when neither value is set. Verified with `helm template`: - default (no overrides) → unchanged labels/annotations - `--set fusion.podLabels.foo=bar --set fusion.podAnnotations.alpha=beta` → both merged into the rendered deployment * feat: add global.podAnnotations for all pods including activity pods Enables service mesh sidecar injection (Istio, Linkerd) and other admission-webhook use cases on connector Job pods, Fusion Spark pods, and all Deployments via a single global.podAnnotations values key. Component-specific podAnnotations override global ones on conflict. Worker reads OLAKE_JOB_POD_ANNOTATIONS and merges into activity pod specs; internal olake.io/* annotations always win. Bumps chart to 0.0.23 / appVersion 0.3.10. * doc: document the podAnnotation flow --------- Co-authored-by: vikash choudhary <vikash@datazip.io> Co-authored-by: Antonio Davide Calì <antoniodavide.cali@zego.com>
vishalm0509
changed the title
hash-data
approved these changes
Jun 24, 2026
shubham19may
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Release olake-worker
v0.3.10, olake-helmv0.0.23Fixes # (issue)
Type of change
How Has This Been Tested?
Screenshots or Recordings
Related PR's (If Any):