From 3f63b3e8645a03e6a8aed2ac64762f6d904aab09 Mon Sep 17 00:00:00 2001 From: Matheus Pimenta <matheuscscp@gmail.com> Date: Thu, 15 May 2025 17:38:33 +0100 Subject: [PATCH] [RFC-0010] Update RFC feature gate behavior Signed-off-by: Matheus Pimenta <matheuscscp@gmail.com> --- rfcs/0010-multi-tenant-workload-identity/README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/rfcs/0010-multi-tenant-workload-identity/README.md b/rfcs/0010-multi-tenant-workload-identity/README.md index d975980f..5c867717 100644 --- a/rfcs/0010-multi-tenant-workload-identity/README.md +++ b/rfcs/0010-multi-tenant-workload-identity/README.md @@ -601,11 +601,7 @@ To enable using the new `serviceAccountName` fields, we propose introducing a feature gate called `ObjectLevelWorkloadIdentity` in the controllers that would support the feature. In the first release we should make it opt-in so cluster admins can consciously roll it out. If the feature gate is disabled -and users set the field in Flux APIs that use the field only for this feature, -a terminal error should be returned. If the feature gate is disabled and users -set the field in Flux APIs that use the field for other purposes, like in the -case of the `OCIRepository` and `ImageRepository` APIs, the controller should -just log a warning and ignore the field. +and users set the field a terminal error should be returned. ### Workload Identity Library -- GitLab