Allow starting without service endpoints #260
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR helps with #222
It allows the start of the first Varnish Pod in a StatefulSet/Deployment before any Varnish Pod IP appears on the service Endpoints list.
When you enable liveness/readiness probes, the first instance is waiting for itself. In this PR, new CLI flags are added to define a timeout for frontends/backends initialization. This allows the first Pod to start anyway.
In the VCL you must handle cases when there are no frontends/backends and the liveness/readiness probe should behave in a way that will eventually allow k8s to add this instance to the endpoint list in the service. After that, the controller renders a new VCL with a non-empty list of frontends/backends.