Allow ClusterOutput and ClusterFlow resources defined in arbitrary namespaces #499
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.
What's in this PR?
Adds an optional, backwards compatible flag to allow using
ClusterOutput
andClusterFlow
resources in arbitrary namespaces. Administrators will still be able to control who has the ability to create such resources through RBAC.Why?
To support use cases where a development team has ownership over logs coming from multiple namespaces but they can only deploy resources into their own namespace and cannot access the logging's control namespace.