Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add section about Flux's cross-namespace policy #1636

Merged
merged 1 commit into from
Aug 25, 2023
Merged

Add section about Flux's cross-namespace policy #1636

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions content/en/flux/security/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,14 +204,18 @@ If the binding is not defined for the correct service account and namespace, it
The roles and permissions for this multi-tenancy approach
are described in detail here: <https://github.com/fluxcd/flux2-multi-tenancy>.

## Cross-Namespace reference policy

Flux's general premise is to follow Kubernetes best RBAC practices which forbid cross-namespace references to potential sensitive data, i.e. Secrets and ConfigMaps. For sources and events, Flux allows referencing resources from other Namespaces. In these cases, the policy is governed by each controller's `--no-cross-namespace-refs` flag. See the [Flux multi-tenancy configuration page](/flux/installation/configuration/multitenancy/) for further information on this flag.

## Further securing Flux Deployments

Beyond the security features that Flux has backed into it, there are further best
Beyond the baked-in security features of Flux, there are further best
practices that can be implemented to ensure your Flux deployment is as secure
as it can be. For more information, checkout the [Flux Security Best Practices](best-practices.md).

[^1]: However, by design cross-namespace references are an exception to RBAC.
Platform admins have to option to turnoff cross-namespace references as described in the
Platform admins have the option to turn off cross-namespace references as described in the
[installation documentation](/flux/installation/configuration/multitenancy/).
[^2]: Platform admins have to option to enforce impersonation as described in the
[installation documentation](/flux/installation/configuration/multitenancy/).