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

VSecM Keystone should bail out and crash if it cannot initialize in timely manner. #1115

Open
v0lkan opened this issue Aug 19, 2024 · 0 comments

Comments

@v0lkan
Copy link
Contributor

v0lkan commented Aug 19, 2024

VSecM Keystone’s init container waits forever for a secret to be assigned to it.

It's better to give it a grace period (like 5 minutes) and let Keystone crash and restart if it cannot fetch the secret in that timeframe.

This requires a modification (and likely an additional env var configuration) for VSecM Init Container.

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

No branches or pull requests

1 participant