Skip to content

[kube-prometheus-stack] Add support for deploying Alertmanager in a custom namespace #5527

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

shafi-elastisys
Copy link

What this PR does / why we need it

This PR introduces support for deploying Alertmanager in a custom namespace by allowing the user to set alertmanager.namespaceOverride. This improves flexibility, especially for multi-namespace or more security-conscious setups, where isolating Alertmanager from other monitoring components is preferred.

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

  • fixes #

Special notes for your reviewer

Checklist

  • DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

Copy link
Member

@jkroepke jkroepke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, to avoid a breaking change, fallback to kube-prometheus-stack.namespace, if kube-prometheus-stack-alertmanager.namespace is not set

Signed-off-by: Mohamed Shafiq <[email protected]>
@shafi-elastisys
Copy link
Author

Fixed with the latest commit.

@shafi-elastisys shafi-elastisys requested a review from jkroepke April 9, 2025 09:28
@jkroepke
Copy link
Member

Please check the CI failures

Signed-off-by: Mohamed Shafiq <[email protected]>
Signed-off-by: Mohamed Shafiq <[email protected]>
Signed-off-by: Mohamed Shafiq <[email protected]>
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.

2 participants