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
{{ message }}
This repository has been archived by the owner on Aug 31, 2022. It is now read-only.
When there are multiple clusters in an area its essential to have the source clustername associated with each event. The event object exposed by Kubernetes provides a clustername, but it does not set it.
We've got some code here in testing that adds an optional "clusterName" to the config file, and if clusterName is set in the config file, then the clusterName is set in the event. This makes it easy to filter a stream of events by source cluster.
A PR will be coming soon pending further testing.
The text was updated successfully, but these errors were encountered:
When there are multiple clusters in an area its essential to have the source clustername associated with each event. The event object exposed by Kubernetes provides a clustername, but it does not set it.
We've got some code here in testing that adds an optional "clusterName" to the config file, and if clusterName is set in the config file, then the clusterName is set in the event. This makes it easy to filter a stream of events by source cluster.
A PR will be coming soon pending further testing.
The text was updated successfully, but these errors were encountered: