-
Notifications
You must be signed in to change notification settings - Fork 74
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
Varnish does not start #168
Comments
Thanks for the report -- This is odd; after the "waiting for initial configuration before starting Varnish" message, the controller should watch the backend endpoints, and render its configuration based on the observed endpoints. It's been a few year since I've last touched that particular piece of code, but I'm wondering if there's an initial kube-httpcache/pkg/watcher/endpoints_watch.go Lines 23 to 27 in 60f555d
Otherwise, the entire startup of the controller would depend on the endpoints object being updated (by chance) to actually start. I'll investigate some more. |
I was able to confirm this issue, in the case (and only then) when the watched backend service did either not exist or have any endpoints. Can you confirm that your backend service both exists and has endpoints when the issue occurs? |
I'm facing the same problem. I could noticed the Note: I'm deploying all the files in a single file. I'll try to do it individually after. |
Nevermind. I was with syntax problems in my Varnish settings. |
Describe the bug
Varnish does not start. No errors in pod's logs
To Reproduce
Steps to reproduce the behavior:
It hangs on
waiting for initial configuration before starting Varnish
Expected behavior
Varnish starts
Environment:
The text was updated successfully, but these errors were encountered: