-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Control plane monitoring with operator on Openshift4 and EKS #32048
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
base: master
Are you sure you want to change the base?
Conversation
Preview links (active after the
|
Created DOCS-12268 to review |
#### Validation | ||
Check that checks are running: | ||
```shell | ||
kubectl exec -it <cluster-agent-pod> -- agent clusterchecks |
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 suggest we remove the -it
as we run a single command and its output will print to the console.
adding the -it
will increase chances of i/o errors when piping the stream to some toole like grep
or less
#### Validation | ||
Check that checks are running: | ||
```shell | ||
kubectl exec -it <cluster-agent-pod> -- agent clusterchecks |
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.
same here suggest we remove the -it
to prevent issue when piping output.
Look for: | ||
- `kube_apiserver_metrics` | ||
- `kube_controller_manager` | ||
- `kube_scheduler` | ||
|
||
You should see control plane metrics in Datadog like: | ||
- `kube_apiserver.*` | ||
- `kube_controller_manager.*` | ||
- `kube_scheduler.*` |
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.
you omit etcd
here is it expected for some reasons ?
What does this PR do? What is the motivation?
This PR updates the public control plane monitoring documentation with new instructions about an automatic way to do this using the Operator (on EKS and Openshift 4). This is largely based on our internal documentation which can be found here.
Currently, this PR frames this as a "Using the Operator" vs "Legacy" methods, but alternative framings are also welcome.
Motivation: https://datadoghq.atlassian.net/browse/CONTINT-4834
Merge readiness: