Skip to content
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

Merged
merged 5 commits into from
Jan 25, 2019

Conversation

bmcustodio
Copy link
Contributor

This PR updates dklb's behaviour in order to use dklb itself as the backend for a given Ingress resource whenever one of the following conditions is met:

  • There is no default backend specified in the Ingress resource;
  • A referenced 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 the kube-system/dklb service is being changed to be of NodePort 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.

@bmcustodio bmcustodio added the wip label Jan 24, 2019
@bmcustodio bmcustodio self-assigned this Jan 24, 2019
@bmcustodio bmcustodio added the feature New feature or request label Jan 24, 2019
@bmcustodio bmcustodio force-pushed the bcustodio/default-backend branch 4 times, most recently from 2de1fdc to b78c984 Compare January 24, 2019 18:17
@bmcustodio bmcustodio force-pushed the bcustodio/default-backend branch from b78c984 to df9ab54 Compare January 24, 2019 18:19
@bmcustodio bmcustodio removed the wip label Jan 24, 2019
@pires pires merged commit 44cff0b into master Jan 25, 2019
@pires pires deleted the bcustodio/default-backend branch January 25, 2019 13:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants