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.
Provides the ability for sharing a provider across namespaces.
Provides the ability for multiple alerts to share the same provider and post to different channels.
This avoids having to create a single provider for each channel created, reducing the number of necessary CRs when a provider can support multiple channels.
This avoids having to create a secret in every namespace that needs to use a provider to send notifications, which might not be desirable not only because of the sheer number of required objects, but also because the secret that the provider uses might not be something we want to share with owners of other namespaces.
Overall, this alleviates the usage of providers and alerts in large multi-tenant environments, as well as in smaller environments that might want to simplify their usage.
This also does not change the current default behaviour. Providers are still namespace bound by default unless specifically allowed in their spec to be used across namespaces, for security reasons.
Addresses #125