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.
Sometime EventReports might contain information that are sensitive and we don't want those stored into the management cluster.
Let's take the DB as a service. When a PG Cluster is created in the service cluster, Sveltos fetches the credentials and store those in the management cluster. But after a Job (accessing the DB) is created in the managed cluster, there is no need to have this information in the management cluster anymore.
So it would be nice to have an option for EventReports to be removed after being consumed by EventTrigger.
This of course means that EventTrigger won't be able to react to any other change (since the EventReport is not present in the management cluster anymore after first time it is consumed)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Sometime EventReports might contain information that are sensitive and we don't want those stored into the management cluster.
Let's take the DB as a service. When a PG Cluster is created in the service cluster, Sveltos fetches the credentials and store those in the management cluster. But after a Job (accessing the DB) is created in the managed cluster, there is no need to have this information in the management cluster anymore.
So it would be nice to have an option for EventReports to be removed after being consumed by EventTrigger.
This of course means that EventTrigger won't be able to react to any other change (since the EventReport is not present in the management cluster anymore after first time it is consumed)
The text was updated successfully, but these errors were encountered: