This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
http: use dklb as the default backend when necessary #9
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 updates
dklb
's behaviour in order to usedklb
itself as the backend for a givenIngress
resource whenever one of the following conditions is met:Ingress
resource;Service
resource is missing or is otherwise invalid.In order for this to work, a new HTTP server that responds to all requests with
503 SERVICE UNAVAILABLE
is being added, and thekube-system/dklb
service is being changed to be ofNodePort
type. The actual node port is dynamically assigned by Kubernetes, as usual, and is discovered by the translator by querying the aforementioned service and handed over to EdgeLB.Unit tests are being updated as required, and new ones (both unit and end-to-end) are being introduced. The documentation is also being updated in order to mention the new feature.