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

on UpSync, allow target ns to be defined in annotation/label #6

Closed
joaocc opened this issue May 21, 2023 · 3 comments
Closed

on UpSync, allow target ns to be defined in annotation/label #6

joaocc opened this issue May 21, 2023 · 3 comments
Labels

Comments

@joaocc
Copy link

joaocc commented May 21, 2023

Hi,
Reposting from [https://github.com/loft-sh/vcluster-sdk/issues/56]
Edited after detecting that it is possible to configure an env variable on the plugin to change the default namespace.

Would it be possible to add an annotation or label with the target namespace to create a specific secret in, in the case of upsync? Even though we can select a default namespace for secrets (via env on the plugin), being able to define this for each secret would make the plugin much more useful... Kind of a cross-cluster-secrets-operator :)
Thx

@github-actions
Copy link

🎉 This issue has been resolved in version 0.1.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@joaocc
Copy link
Author

joaocc commented May 24, 2023

Thanks. How ofter is the plugin synchronizing secrets? Thx

@paddatrapper
Copy link
Contributor

It is controlled by VCluster's reconciliation period, so you'll have to look at what their documentation/code is doing to answer that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants