From 43372a9ac74c768297477901deb4668a793a7b76 Mon Sep 17 00:00:00 2001 From: Stefan Prodan Date: Thu, 13 Jan 2022 13:09:49 +0200 Subject: [PATCH] Add network policies reference Signed-off-by: Stefan Prodan --- rfcs/0002-source-acl/README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/rfcs/0002-source-acl/README.md b/rfcs/0002-source-acl/README.md index 5564d9dd..d9bc29df 100644 --- a/rfcs/0002-source-acl/README.md +++ b/rfcs/0002-source-acl/README.md @@ -5,9 +5,17 @@ Cross-namespace references to Flux sources should be subject to Access Control Lists (ACLs) as defined by the owner of a particular source. +Similar to [Kubernetes Network Policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/), +Flux ACLs define policies for restricting the access to the source artifact server based on the +caller's namespace. + ## Motivation -As of v0.23.0, Flux allows for `Kustomizations` and `HelmReleases` to reference sources in different namespaces. +This proposal tries to solve the "cross-namespace references side-step namespace isolation" issue (explained in +[RFC-0001](https://github.com/fluxcd/flux2/tree/main/rfcs/0001-authorization#cross-namespace-references-side-step-namespace-isolation)). + +As of [version 0.25](https://github.com/fluxcd/flux2/releases/tag/v0.25.0) (Ian 2022), +Flux allows for `Kustomizations` and `HelmReleases` to reference sources in different namespaces. This poses a serious security risk for multi-tenant environments as Flux does not prevent tenants from accessing known sources outside of their namespaces.