-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
doc issue related to monitor part #3111
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Just one minor comment.
docs/user-guide/monitoring.md
Outdated
@@ -44,7 +44,7 @@ kubectl get svc -n ingress-nginx | |||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE | |||
default-http-backend ClusterIP 10.103.59.201 <none> 80/TCP 3d | |||
ingress-nginx NodePort 10.97.44.72 <none> 80:30100/TCP,443:30154/TCP,10254:32049/TCP 5h | |||
prometheus NodePort 10.98.233.86 <none> 9090:32630/TCP 1m | |||
prometheus-service NodePort 10.98.233.86 <none> 9090:32630/TCP 1m |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd change the name in the manifest, service is redundant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from the doc, the service was created with https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/monitoring/prometheus.yaml.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's exactly what I meant, please change the name in the manifest, not in the docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so should we also need to update the prometheus-server
to prometheus
in manifest as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No this is fine. What I want to avoid is the use of Kubernetes object types in Kubernetes object names (e.g. myapp-pod
, myapp-deployment
, myapp-service
are generally considered as bad names).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, I see.
e6dde4d
to
69d132a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hchenxa I'm so sorry it looks like I spoke too fast 🙈
The original intention was to use the name prometheus-servER
everywhere, service
was a typo.
Again, sorry for wasting your time on this.
The Service should be called prometheus-server
.
69d132a
to
89cf832
Compare
@antoineco , it's ok, thanks for reviewing. |
/lgtm |
89cf832
to
be87141
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: antoineco, hchenxa The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
there have some doc issue related to monitoring part.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer: