Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PushSecret/Kubernetes: allow cloning of Secrets across clusters #2836

Open
2 tasks
moolen opened this issue Nov 2, 2023 · 3 comments
Open
2 tasks

PushSecret/Kubernetes: allow cloning of Secrets across clusters #2836

moolen opened this issue Nov 2, 2023 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@moolen
Copy link
Member

moolen commented Nov 2, 2023

As a user i want to be able to clone a secret from one cluster to another using PushSecret. At the moment we can only push individual keys, not the whole secret.

Prerequisites:

Once merged we need to implement the provider-specific bits.

This relates to #2166 and the cross-cluster secret push can be implemented with this feature, however do also want to make it work without having to define a template.

AC:

  • users are able to clone a secret across clusters using PushSecret
  • we have end-to-end tests to cover this scenario
@moolen moolen added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 2, 2023
@moolen moolen added this to the Push Secret beta milestone Nov 2, 2023
@moolen moolen changed the title PushSecret/Kubernetes: allow cloning of Secrets PushSecret/Kubernetes: allow cloning of Secrets across clusters Nov 2, 2023
@pre
Copy link

pre commented Nov 4, 2023

Cloning of Secrets should also include the ability to clone the metadata.labels of these secrets.

It’s typical that Secrets be found with label search by code (in addition to mounting them by name).

Currently PushSecret only copies the data of the Secret - cloning of labels are not supported at all.

@pre
Copy link

pre commented Apr 30, 2024

Now that the dependency #2862 (follow up of #2288) has been merged, are there any other known blockers for being able support cloning of the whole Secret?

@ron1
Copy link
Contributor

ron1 commented Apr 30, 2024

See issue #3353

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: No status
Development

No branches or pull requests

3 participants