-
Notifications
You must be signed in to change notification settings - Fork 39
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
ingress: use exact path #99
ingress: use exact path #99
Conversation
7bb7f48
to
e2a3252
Compare
@AlexanderYastrebov can you elaborate on why this change is needed ? it would prevent e.g. fetching |
|
in our environment, we also use other endpoints, and I don't think it would be good changing the default prefixPath for everyone. however, if you want to make that configurable in the Helm Chart, I would merge it 🙃 please rebase your branch on master, as I pushed a few CI fixes, and make your pathType prefix configurable from within values.yaml, and we will look at it again. |
Do you use other endpoints from outside of kubenurse? I thought this ingress is dedicated to kubenurse and kubenurse ingress checker does not use any other endpoint. Per-pod metrics should not be collected via ingress anyways. My point is that this might be a security issue if someone deploys kubenurse with public hostname and thus exposes /metrics to the internet. |
kubenurse/internal/kubenurse/server.go Lines 142 to 146 in c4bf82f
while I agree this is not best practice to have that exposed through an ingress, it is sometimes useful in our environments to take a look at those values. also, at this point, I don't think changing the default behaviour of the helm chart makes sense, as other people might be using my point is that while your proposal is very valid (and it should have been done like that from the beginning), I'm not going to change the default behaviour of the Helm Chart. I'd be really happy if you updated your PR to make the ingress prefixPath configurable 🙃 |
Sorry, I do not know much about Helm. |
No description provided.