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

Manual trigger for update resync in Kubernetes operator #1808

Open
rounakdatta opened this issue May 9, 2024 · 0 comments
Open

Manual trigger for update resync in Kubernetes operator #1808

rounakdatta opened this issue May 9, 2024 · 0 comments
Labels
🚀 feature request New feature or request k8-operator Related to k8-operator

Comments

@rounakdatta
Copy link

Feature description

As far as I explored, there's no provision to manually trigger a resync for the Kubernetes operator. While the resyncInterval is good enough for our use case, we wanted to have a manual way of triggering a sync via the dashboard.

Why would it be useful?

We'd be setting up Infisical in a way that there'd be a huge number of InfisicalSecret instances in a single cluster, and thereby all of them handled by a single operator pod. Hence, to reduce serving load on our self-hosted Infisical server, we want to have a big value for resyncInterval. Also, we'd not push out updates to secrets very often, however when we do, we'd like it to be reflected soon. We think having an option for manual trigger on the dashboard is a nice way to go about it.

@akhilmhdh akhilmhdh added 🚀 feature request New feature or request k8-operator Related to k8-operator labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 feature request New feature or request k8-operator Related to k8-operator
Projects
None yet
Development

No branches or pull requests

2 participants