feat(fusion): add podLabels and podAnnotations hooks

[antoniocali]

Summary

Every other component in this chart — olake-ui, olake-worker, temporal, postgresql, nfs-server, elasticsearch — exposes podLabels and podAnnotations value blocks that get merged into spec.template.metadata. The Fusion deployment template is the only one missing both. Its pod-template metadata is hardcoded to the app.kubernetes.io/* labels and the config-checksum annotation, with no operator extension point.

This matters for deployments running under K8s admission policies that require specific labels on pod templates (Gatekeeper / Kyverno / OPA constraints, internal compliance tags, mesh-routing labels, etc.). Without a podLabels hook, operators either have to live with policy warnings on the Fusion pod or carry a parent-chart patch.

Real-world example: my deployment runs under a Gatekeeper template-required-labels-warn constraint requiring meta.zego.tools/{managed-from, owner, service} on every pod template. I can satisfy this for olake-ui / olake-worker / temporal / postgresql via their existing podLabels blocks, but the Fusion pod can't be reached without forking the chart.

Changes

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.

Verification

# Default: unchanged labels/annotations
helm template test helm/olake --set fusion.enabled=true

# Overrides: both merged into the rendered deployment
helm template test helm/olake --set fusion.enabled=true \
  --set fusion.podLabels.foo=bar \
  --set fusion.podAnnotations.alpha=beta

Both render as expected — no other resources touched.

Scope

Single template + matching values.yaml defaults. Mirrors existing conventions in this chart. No breaking change.

[saptarshi-datazip]

Hello @antoniocali , is this a blocker for you?
We are planning a release by next Tuesday and plan to release this fix along with it. If it is urgent then we can release this fix as a standalone by EOD.

[antoniocali]

Hello @antoniocali , is this a blocker for you?
We are planning a release by next Tuesday and plan to release this fix along with it. If it is urgent then we can release this fix as a standalone by EOD.

Hello

Not a blocker at all