[DOCS-9152] adding more information to kube_api_server check

[aliciascott]

What does this PR do?

Motivation

Support request:
DOCS-9152

Additional Notes

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Changelog entries must be created for modifications to shipped code
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[L3n41c]

I just have a small doubt regarding the type of checks that we would like to use for kube_apiserver_metrics.

• With a service check, all the apiserver instances (several different sources) will feed the same timeseries.
• With an endpoint check, each apiserver instance will have its own timeseries.

I think we want the second type.
At least, that’s what is currently recommended in the check : https://github.com/DataDog/integrations-core/tree/master/kube_apiserver_metrics#configuration

[neko-dd]

Created DOCS-9275 for review

[rtrieu]

Some minor feedback, but otherwise a great update. Thanks!

[aliciascott]

/merge

[dd-devflow]

🚂 MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

Use /merge -c to cancel this operation!

[dd-devflow]

🚂 MergeQueue: This merge request was already merged

This pull request was merged directly.