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

Default local/private endpoints #4

Closed
birgirst opened this issue Jul 1, 2019 · 1 comment · Fixed by #66
Closed

Default local/private endpoints #4

birgirst opened this issue Jul 1, 2019 · 1 comment · Fixed by #66

Comments

@birgirst
Copy link
Contributor

birgirst commented Jul 1, 2019

Some HTTP endpoints exposed by applications deployed by FIAAS should generally not be available from the internet/outside the Kubernetes cluster. Typically this will be prometheus metrics endpoints, health endpoints and so on. Currently the defaults for these endpoints provided by FIAAS are grouped under /_/. This means that one way to solve this could be to employ the default that /_/* should be considered private by the ingress controller.

@mortenlj
Copy link
Member

We should probably just document this expectation, but it should also probably integrate in some way with #8.

mortenlj added a commit that referenced this issue Jan 13, 2020
The intention when deciding on defaults for v3 was to enable some conventions that would make operating a cluster easier.
One such convention was the `/_/` prefix for "internal" paths. Operators might want to block access from the public internet to any path starting with this prefix.

Fixes #4
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 a pull request may close this issue.

2 participants