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

shelob: changes to where internal things are served #30

Merged
merged 1 commit into from
Nov 21, 2019

Conversation

johanot
Copy link
Contributor

@johanot johanot commented Nov 20, 2019

read on:

  • /status is still served on the regular web port, but is only served if there are no applications deployed that matches the input host header
  • /api/applications and the html applications view (served on /) is moved the the admin port
  • /metrics are now only served on the admin port

the check "routeToSelf" that previously special-cased the host header "localhost" has been removed.

read on:

- /status is still served on the regular web port, but is only served if there are no applications deployed that matches the input host header
- /api/applications and the html applications view (served on /) is moved the the admin port
- /metrics are now only served on the admin port

the check "routeToSelf" that previously special-cased the host header "localhost" has been removed.
Copy link
Contributor

@srhb srhb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good enough for me!

@adamtulinius adamtulinius self-requested a review November 21, 2019 09:23
@adamtulinius adamtulinius merged commit 8e3b618 into master Nov 21, 2019
@adamtulinius adamtulinius deleted the remove-route-to-self branch November 21, 2019 09:27
@johanot
Copy link
Contributor Author

johanot commented Nov 21, 2019

I (re-)investigated the possibility of a solution where the status endpoint has it's own "vhost", requiring a special host-header to get the status-response:

It would require:

  1. An extra cmd-line flag for Shelob allowing you to configure which hostname(s) to respond to /status for.

  2. Possibly a change to sofk8s, allowing for sofk8s to request with a custom host-header. (current behavior: Host: shelob.shelob.svc.cloud.dbc.dk:80), we probably want: k8s.dbc.dk.

  3. Telling the k8s readiness check to request with a custom host-header. (current behavior: no host-header).

If all of the above are implemented, I think that solution has the potential for being nicer, than the current one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants