From df57392f4871c4929cbaf3d8f2da264e886f8a36 Mon Sep 17 00:00:00 2001 From: Stefan Prodan Date: Sat, 30 Aug 2025 12:41:13 +0300 Subject: [PATCH] Add Feature Gate Signed-off-by: Stefan Prodan --- rfcs/0000-external-artifact/README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/rfcs/0000-external-artifact/README.md b/rfcs/0000-external-artifact/README.md index 912dced1..e48a0ef1 100644 --- a/rfcs/0000-external-artifact/README.md +++ b/rfcs/0000-external-artifact/README.md @@ -300,6 +300,17 @@ to trace any Kubernetes resource in-cluster that originates from an `ExternalArt The `flux` CLI will implement the `flux get externalartifact` command for listing and status checking of `ExternalArtifact` custom resources in the cluster. +### Feature Gate + +While the `ExternalArtifact` API will be available out of the box with Flux, +the ability for `kustomize-controller` and `helm-controller` to consume artifacts +from `ExternalArtifact` resources will be behind a feature gate called `ExternalArtifact`. + +The feature gate will be disabled by default and can be enabled by setting +the `--feature-gates=ExternalArtifact=true` flag on the `kustomize-controller` +and `helm-controller` deployments. This allows cluster administrators to +control the adoption of the `ExternalArtifact` feature in their clusters. + ## Implementation History