Skip to content
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

Allow disabling cross-namespace event sources #319

Merged
merged 1 commit into from
Jan 28, 2022

Conversation

stefanprodan
Copy link
Member

@stefanprodan stefanprodan commented Jan 27, 2022

On multi-tenant clusters, platform admins can disable cross-namespace event sources with the --no-cross-namespace-refs=true flag. When this flag is set, alerts can only refer to event sources in the same namespace as the alert object, preventing tenants from subscribing to anther tenant's events.

When the controller drops an event due to --no-cross-namespace-refs=true it logs:

alert 'tenant1/slack' can't process event from 'HelmRelease/tenant2/app', cross-namespace references have been blocked

Part of: fluxcd/flux2#2337

@stefanprodan stefanprodan added enhancement New feature or request area/alerting Alerting related issues and PRs labels Jan 27, 2022
@stefanprodan stefanprodan force-pushed the no-cross-namespace-refs branch 4 times, most recently from 4d8b20d to b85e902 Compare January 27, 2022 18:22
@stefanprodan stefanprodan force-pushed the no-cross-namespace-refs branch 3 times, most recently from adefa11 to 50ad628 Compare January 28, 2022 07:34
Introduce the flag `--no-cross-namespace-refs` (defaults to false) for allowing cluster admins to disable cross-namespace event sources for alerts.

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
@stefanprodan stefanprodan force-pushed the no-cross-namespace-refs branch from 50ad628 to 44c08a2 Compare January 28, 2022 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/alerting Alerting related issues and PRs enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants