acoustic-carpenter-78188
07/04/2023, 3:05 PMflyte-binary chart to K8s environments where they don't have cluster-wide permissions but are more or less constrained to what can be done on a single namespace.
As a way to prepare Flyte for enterprise environments where potential attack surface is a concern and the principle of least privilege is observed, creating a path for single-namespace deployment of Flyte would be useful.
Goal: What should the final outcome look like, ideally?
Make he RBAC to be namespaced, flyte-binary/flytepropeller set to watch a single namespace, and namespace mapping for project/domains fixed to the single namespace
Describe alternatives you've considered
None
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyte