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
Nice tool! I was wondering whether the reflector could be enhanced with a feature to omit certain namespaces from being the "source" of the reflection. Rational could be that you want to be in control of what secret is mirrored somewhere. If you're not the only one that has access to the cluster, someone else could just annotate a secret and the reflector would mirror it somewhere else.
This could be implemented in a allow-list and deny-list style feature, so that users can configure it depending their use cases.
What do you think?
The text was updated successfully, but these errors were encountered:
Nice tool! I was wondering whether the reflector could be enhanced with a feature to omit certain namespaces from being the "source" of the reflection. Rational could be that you want to be in control of what secret is mirrored somewhere. If you're not the only one that has access to the cluster, someone else could just annotate a secret and the reflector would mirror it somewhere else.
This could be implemented in a allow-list and deny-list style feature, so that users can configure it depending their use cases.
What do you think?
The text was updated successfully, but these errors were encountered: