Mirrors/flux2
1
0
Fork 0
mirror of synced 2026-03-14 23:46:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Mark RFC 0010, 0011 and 0012 as implemented

Browse Source 
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan
2026-03-13 21:45:08 +02:00
parent e9226713e8
commit 64e18014c3
3 changed files with 16 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
rfcs/0010-multi-tenant-workload-identity/README.md
View File

@@ -1,15 +1,10 @@
# RFC-0010 Multi-Tenant Workload Identity
**Status:** implementable
<!--
Status represents the current state of the RFC.
Must be one of `provisional`, `implementable`, `implemented`, `deferred`, `rejected`, `withdrawn`, or `replaced`.
-->
**Status:** implemented
**Creation date:** 2025-02-22
**Last update:** 2025-04-29
**Last update:** 2026-03-13
## Summary
@@ -1420,10 +1415,11 @@ options to call `gcp.NewTokenSource()` and feed this token source to the
`HelmRepository` and `HelmChart`, as well as for SOPS decryption
in the `Kustomization` API and Azure Event Hubs in the
`Provider` API.
<!--
Major milestones in the lifecycle of the RFC such as:
- The first Flux release where an initial version of the RFC was available.
- The version of Flux where the RFC graduated to general availability.
- The version of Flux where the RFC was retired or superseded.
-->
* In Flux 2.7 object-level workload identity was introduced for all
the remaining APIs that support cloud providers, i.e. `Bucket`,
`GitRepository` and `ImageUpdateAutomation`, and also all the
remaining types for the `Provider` API, i.e. `azuredevops` and
`googlepubsub`. In addition, support for controller and
object-level workload identity was introduced for the
`Kustomization` and `HelmRelease` APIs for remote cluster
access.