feat: add managed afinity rules to helm-charts - #104
Merged
almeidabbm merged 2 commits intoJan 13, 2026
Merged
Conversation
ZeRego
approved these changes
Jan 13, 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
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.

Add High Availability Features to Lightdash Helm Chart
Relates to: https://linear.app/lightdash/issue/PROD-2405/gcp-alert-failure-of-uptime-check-id-staging-lightdash-cloud
Relates to: https://linear.app/lightdash/issue/PROD-2444/gcp-alert-failure-of-uptime-check-id-lightdash-cloud-us-f6pmvbw1bso
Relates to: https://linear.app/lightdash/issue/PROD-2400/gcp-alert-failure-of-uptime-check-id-lightdash-cloud-us-f6pmvbw1bso
TL;DR
Added pod anti-affinity and improved documentation for high availability configurations in the Lightdash Helm chart.
What changed?
Why make this change?
This change enhances the Helm chart's ability to deploy Lightdash in a highly available configuration. By adding pod anti-affinity rules, we can ensure that pods are distributed across different nodes and availability zones, reducing the risk of downtime during node maintenance or failures. The implementation is flexible, allowing users to choose between hard constraints (required) and soft preferences (best-effort) for both node and zone distribution.
Worker
Backend