Support cluster-scoped generators (specifically Password)

[cten]

Describe the solution you'd like I would like to declare a Password Generator that adheres to my requirements (length, complexity) once then re-use across all namespaces.

What is the added value? I don't have to create the same Password Generator in multiple namespaces. Cleaner.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[cten]

Keep alive

[Davidffry]

Have you find a workaround ?

[moolen]

There's no workaround. We'll need a new Kind to make generators cluster-scoped.

I've created a new Milestone to track enhancements around Generators, it seems there's interest in this from the community.

[Davidffry]

Thanks you, I'll follow this.

[erikzele]

I'm facing same issue with ecrauthorizationtokens and fakes generators, when trying to create following chain: clusterexternalsecret, fake, ecrauthorizationtokens -> externalsecret (per matching namespaces) -> secret (per matching namespaces)

[avosepp]

I'm tagging along here. I would like to create ACRGenerators at a cluster level, so that individual namespaces can request pull credentials for the container registry. If I have to apply the ACR Generator on a per-namespace level I might as well just apply a dockerconfig secret.

It would be great to get cluster scoped generators.

[TheBritz]

+1 to this, would like to use ClusterExternalSecrets with a generator

[alexzandershevchenko]

+1. Want to have ECRAuthorizationToken generator cluster scoped to update imagePullSecret's secret in multiple namespaces using ClusterExternalSecret... For now, had to make dirty hack via storing username/password in SecretStore/ClusterSecretStore using PushSecret and then reuse those via creating additional ClusterExternalSecret :(