-
Notifications
You must be signed in to change notification settings - Fork 61
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
Update Monitoring doc #379
Conversation
prometheus.io/path: ... | ||
prometheus.io/port: ... | ||
prometheus.io/scrape: ... | ||
- job_name: 'kubernetes-service-endpoints' |
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.
How are we targeting this specific service? I think we need to add a keep action for __meta_kubernetes_service_annotation_prometheus_io_port
.
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.
We are not. It is generic configuration. User may have already have this configuration to monitor other resources. So, they don't need to update anything.
``` | ||
|
||
Now, the below yaml is used to deploy Prometheus in kubernetes: | ||
**Create RBAC:** |
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.
Why do we add this section separately? We should just add this into the deployment.yaml and always create the RABC objects.
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.
Just to make users aware of what RBAC permissions are given.
Task: