You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ability for a ResourceDistribution to point at an existing secret to sync to other namespaces
Why is this needed:
Some tools such as cert-manager create the secret that needs to be synced to other namespaces. It can not easily be created in the ResourceDistribution object itself.
The text was updated successfully, but these errors were encountered:
can you describe the use case in more detail ? what kind of secrets and why it should be sync to other namespaces? If ResourceDistribution can reference an existing secret, it will be a potential security problem. Kruise cannot tell whether the user has the privilege to read the existing secret, sync the secret to a namespace of an un-authorized user is dangerous.
What would you like to be added:
The ability for a ResourceDistribution to point at an existing secret to sync to other namespaces
Why is this needed:
Some tools such as cert-manager create the secret that needs to be synced to other namespaces. It can not easily be created in the ResourceDistribution object itself.
The text was updated successfully, but these errors were encountered: