Skip to content

docs: Update Slack link in repo#171

Merged
shubham19may merged 8 commits into
stagingfrom
docs/readme_update
Jun 25, 2026
Merged

docs: Update Slack link in repo#171
shubham19may merged 8 commits into
stagingfrom
docs/readme_update

Conversation

@nayanj98

@nayanj98 nayanj98 commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

Description

Replaces outdated direct Slack invite links (join.slack.com/t/getolake/...) with the canonical community URL https://olake.io/slack/ across all documentation and the Helm chart landing page.

This keeps Slack links consistent and avoids broken or expired invite URLs.

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Scenario A
  • Scenario B

Screenshots or Recordings

Related PR's (If Any):

vikaxsh and others added 8 commits May 20, 2026 19:13
chore: staging -> master - worker v0.3.6
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
chore: staging -> master (worker v0.3.7, helm v0.0.19)
chore: staging -> master (worker v0.3.8, helm v0.0.20)
chore: staging -> master (olake-helm v0.0.21, olake-worker 0.3.9)
chore: staging -> master (olake-helm v0.0.22)
chore: staging->master (olake-worker v0.3.10, olake-helm v0.0.23)
@nayanj98 nayanj98 changed the title Docs/readme update docs: Update Slack link in repo Jun 25, 2026
@shubham19may shubham19may merged commit 6d2b8a7 into staging Jun 25, 2026
4 checks passed
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.

6 participants