-
Notifications
You must be signed in to change notification settings - Fork 6
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
VZ-5852: Updates for Prometheus Operator #534
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.
Few minor edits
--- | ||
|
||
### Kubernetes cluster monitors are in a "DOWN" state | ||
When viewing targets in the Prometheus console some Kubernetes cluster monitors may be down (`kube-etcd`, `kube-proxy`, etc.) This is likely caused by the configuration of the Kubernetes cluster |
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.
(kube-etcd
, kube-proxy
, etc.) -> (kube-etcd
, kube-proxy
, and such). (period)
|
||
### Kubernetes cluster monitors are in a "DOWN" state | ||
When viewing targets in the Prometheus console some Kubernetes cluster monitors may be down (`kube-etcd`, `kube-proxy`, etc.) This is likely caused by the configuration of the Kubernetes cluster | ||
itself. Depending on the type of cluster certain metrics may be disabled by default. Enabling metrics is cluster dependent so refer to the documentation for your cluster type for details. |
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.
type of cluster -> type of cluster, (comma)
is cluster dependent -> is cluster dependent; (semi-colon)
so refer to the documentation for your cluster type for details -> for details, refer to the documentation for your cluster type.
When viewing targets in the Prometheus console some Kubernetes cluster monitors may be down (`kube-etcd`, `kube-proxy`, etc.) This is likely caused by the configuration of the Kubernetes cluster | ||
itself. Depending on the type of cluster certain metrics may be disabled by default. Enabling metrics is cluster dependent so refer to the documentation for your cluster type for details. | ||
|
||
For example, to enable `kube-proxy` metrics on KinD clusters, edit the `kube-proxy` configmap: |
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.
KinD -> Kind (Oracle Style Guide decision for how to write this product name)
configmap -> ConfigMap (to be consistent with the VZ documentation)
``` | ||
$ kubectl edit cm/kube-proxy -n kube-system | ||
``` | ||
Replace the `metricsBindAddress` value with the following and save the configmap: |
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.
configmap -> ConfigMap
$ kubectl delete pod -l k8s-app=kube-proxy -n kube-system | ||
``` | ||
|
||
See this GitHub [issue](https://github.com/prometheus-community/helm-charts/issues/204) for additional information. |
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.
re-write -> For more information, see this GitHub issue.
``` | ||
metricsBindAddress: 0.0.0.0:10249 | ||
``` | ||
Then restart the `kube-proxy` pods: |
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.
Then -> Then, (comma)
Update the Prometheus info on the Application Deployment guide page and add a Prometheus troubleshooting page.