[RFC-0010] Update RFC feature gate behavior

Signed-off-by: Matheus Pimenta <matheuscscp@gmail.com>
pull/5355/head
Matheus Pimenta 4 weeks ago
parent 656d9d892d
commit 3f63b3e864
No known key found for this signature in database
GPG Key ID: DE594AAD698A94DE

@ -601,11 +601,7 @@ To enable using the new `serviceAccountName` fields, we propose introducing
a feature gate called `ObjectLevelWorkloadIdentity` in the controllers that a feature gate called `ObjectLevelWorkloadIdentity` in the controllers that
would support the feature. In the first release we should make it opt-in so 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 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, and users set the field a terminal error should be returned.
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.
### Workload Identity Library ### Workload Identity Library

Loading…
Cancel
Save