You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A team that has to deploy cluster wide logging rules - without having access to the logging's control namespace - currently has no good options since ClusterFlow and ClusterOutput are namespaced resources.
Describe solution and alternatives you've considered
They would either define ClusterFlow and ClusterOutput as cluster scoped resources, but that would require these resource types to be changed which would be backwards incompatible with older clients.
The other option would be to make the ClusterFlow and ClusterOutput resources available for the logging system from any/all namespaces.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A team that has to deploy cluster wide logging rules - without having access to the logging's control namespace - currently has no good options since ClusterFlow and ClusterOutput are namespaced resources.
Describe solution and alternatives you've considered
They would either define ClusterFlow and ClusterOutput as cluster scoped resources, but that would require these resource types to be changed which would be backwards incompatible with older clients.
The other option would be to make the ClusterFlow and ClusterOutput resources available for the logging system from any/all namespaces.
The text was updated successfully, but these errors were encountered: