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

Custom reloader init containers cannot start in vmauth and vmagent pods #770

Closed
ebensom opened this issue Oct 2, 2023 · 1 comment · Fixed by #771
Closed

Custom reloader init containers cannot start in vmauth and vmagent pods #770

ebensom opened this issue Oct 2, 2023 · 1 comment · Fixed by #771
Labels
bug Something isn't working

Comments

@ebensom
Copy link
Contributor

ebensom commented Oct 2, 2023

The PR #667 introduced using custom reloader init containers for vmauth and vmagent to initialize the configuration.
However there is a bug in the PR blocking the init containers to execute properly:

flag provided but not defined: -mode
v0.38.0

The config-reloader application introduced the --only-init-config for the initialization scenario (i.e. to exit from waiting for subsequent events during watcher initialization), however the vm-operator factory code uses --mode=one-shot argument.

@f41gh7
Copy link
Collaborator

f41gh7 commented Oct 5, 2023

@f41gh7 f41gh7 closed this as completed Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants