Matheus Pimenta
Matheus Pimenta
That OCIRepository could contain a kustomization generating a ConfigMap from that admins-only.yaml file and then you could deploy the ConfigMap with a Flux Kustomization, then you could pull in the...
You can actually let the eventual consistency help you in this case, the ConfigMap and HelmRelease can be applied by the same Kustomization. If helm-controller happens to be faster than...
@mprince We have no plans on the roadmap for integrating this provider, but we can accept contributions and commitment to maintain it on the long-term
The same process described [here](https://github.com/fluxcd/notification-controller/issues/1047#issuecomment-2708087500) can be used for the implementation, replacing the access scope by the scope of Azure DevOps which we already have [here](https://github.com/fluxcd/pkg/blob/8b1f852228b117123efcc7b5708ce112801416b6/auth/azure/client.go#L36). The access token acquired...
Does applying with the helm CLI work for that specific scenario?
This will be supported at the controller level starting with Flux 2.6 for some APIs, then for all APIs in Flux 2.7. Track progress here: https://github.com/fluxcd/flux2/issues/5022 In the future we...
Supporting this for object-level workload identity is easy: Among the three cloud providers only GCP needs changes in our code. The `auth.Provider.GetAudience()` interface needs to receive a `serviceAccount` parameter. In...
Fixed here: https://github.com/fluxcd/pkg/pull/908
Not yet, sorry!
@dgunzy If you have the time and interest, could you please work on this one too?