Add agent_on_k8s docs and k8s provider #401
Conversation
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
ChrsMark
requested review from
ph,
masci,
jsoriano,
blakerouse and
dedemorton
|
A docs preview will be available soon: |
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
docs/en/ingest-management/elastic-agent/running-on-kubernetes-standalone.asciidoc
Outdated
Show resolved
Hide resolved
docs/en/ingest-management/elastic-agent/running-on-kubernetes-standalone.asciidoc
Outdated
Show resolved
Hide resolved
| 1. Kubernetes integration to collect k8s metrics from each nodes' kubelet | ||
| 2. Kubernetes integration to collect metrics from `kube-state-metrics`. https://github.com/kubernetes/kube-state-metrics#usage[kube-state-metrics] is needed to be already deployed | ||
| in the cluster. If `kube-state-metrics` is not already running, deploy it now (see the | ||
| https://github.com/kubernetes/kube-state-metrics#kubernetes-deployment[Kubernetes | ||
| deployment] docs) | ||
| 3. Kubernetes integration to collect metrics from `proxy` kubernetes component on each of the nodes. | ||
| 4. Kubernetes integration to collect metrics from Kubernetes API server, Scheduler and Controller-manager | ||
| 5. System integration to collect system level metrics from nodes. | ||
| 6. Pod's log collection using <<kubernetes-provider,dynamic inputs and kubernetes provider>> |
There was a problem hiding this comment.
This may be too detailed, and it will be easy to forget to update if manifests are modified to include more things.
Perhaps we can rephrase it to don't detail so much what specific components are collected metrics from. We could also include references to the docs of dashboards or UIs where this data can be visualized.
There was a problem hiding this comment.
👍🏼 I made it shorter and more abstract. I like the idea of linking each integration to its respective page (Kubernetes integration/package, System Integration/package etc) however I'm not sure what would be the proper page to choose. Currently we have an Integrations page (https://www.elastic.co/integrations?solution=all-solutions&category=kubernetes) but this refers to Beats integrations and not to packages 🤔 . @dedemorton any ideas here?
There was a problem hiding this comment.
Yep, maybe this is not needed, specially thinking that this is a "running on..." page and there will be more pages with info about UIs and so on.
Signed-off-by: ChrsMark <chrismarkou92@gmail.com>
| ------------------------------------------------ | ||
|
|
||
| [float] | ||
| ==== Autodiscover targeted Pods |
There was a problem hiding this comment.
This is great for the docs!
|
@ChrsMark What is the release target for the doc 7.13? |
@ph I think it will depend on #401 (comment) and what we will decide about the target version of manifests. |
Co-authored-by: Brandon Morelli <bmorelli25@gmail.com> Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co> Co-authored-by: Brandon Morelli <bmorelli25@gmail.com> Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co> Co-authored-by: Chris Mark <chrismarkou92@gmail.com> Co-authored-by: leahleahy <82116004+leahleahy@users.noreply.github.com>
Co-authored-by: Brandon Morelli <bmorelli25@gmail.com> Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co> Co-authored-by: Brandon Morelli <bmorelli25@gmail.com> Co-authored-by: Brandon Morelli <brandon.morelli@elastic.co> Co-authored-by: Chris Mark <chrismarkou92@gmail.com> Co-authored-by: leahleahy <82116004+leahleahy@users.noreply.github.com>
This PR adds documentation for:
Closes elastic/beats#21848
Part of elastic/beats#23613
Kubernetes provider implementation PR: elastic/beats#21480