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

Add support for separate Kubernetes cluster SecretStore #69

Open
mcavoyk opened this issue Oct 18, 2020 · 0 comments
Open

Add support for separate Kubernetes cluster SecretStore #69

mcavoyk opened this issue Oct 18, 2020 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@mcavoyk
Copy link
Collaborator

mcavoyk commented Oct 18, 2020

Describe the solution you'd like
Add SecretStore for secrets store in another cluster (namespace or cluster-wide).

Describe alternatives you've considered
Moving secrets to cloud provider secret and each each cluster having a SecretStore which has authentication to the cloud provider store.

Additional context
Our use-case is that due to network partition, one cluster has access to a secret backend, but other clusters do not. The cluster with network access to the secret backend is accessible to other clusters, so this could provide a link if needed to secrets from the other cluster.

May need more thought, some ideas around only accessing explicit Secrets which already exist, or whether relaying ExternalSecrets is allowed (e.g. ExternalSecret in Cluster B creates new ExternalSecret in cluster A which which has access, secret is propogated to cluster B to be used by workloads).

/kind feature

@mcavoyk mcavoyk added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 18, 2020
@mcavoyk mcavoyk changed the title Add support for Kubernetes cluster SecretStore Add support for separate Kubernetes cluster SecretStore Oct 18, 2020
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
None yet
Development

No branches or pull requests

1 participant