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
I'm interested in adopting KGateway, however my organization has tight controls around access to certain things, such as secrets. In particular granting cluster-level access to secrets, which the KGateway control plane looks for.
I know you can configure the config discovery to filter for certain namespaces using "discoveryNamespaceSelectors". But the control plane still requires cluster level access to config by default. This is problematic from a security standpoint.
Is there currently any way to restrict config syncing to the namespace level, using namespace level permissions? And if not, is there any plan to implement this?
Thank you very much for your help, and for all your work on this project!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello KGateway maintainers,
I'm interested in adopting KGateway, however my organization has tight controls around access to certain things, such as secrets. In particular granting cluster-level access to secrets, which the KGateway control plane looks for.
I know you can configure the config discovery to filter for certain namespaces using "discoveryNamespaceSelectors". But the control plane still requires cluster level access to config by default. This is problematic from a security standpoint.
Is there currently any way to restrict config syncing to the namespace level, using namespace level permissions? And if not, is there any plan to implement this?
Thank you very much for your help, and for all your work on this project!
All reactions