Add how-to for testing elastic-agent on k8s#28697
Add how-to for testing elastic-agent on k8s#28697tetianakravchenko merged 3 commits intoelastic:masterfrom
Conversation
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
|
This pull request does not have a backport label. Could you fix it @tetianakravchenko? 🙏
NOTE: |
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
ChrsMark
left a comment
There was a problem hiding this comment.
Thank you for adding this! Looks good over and the place for this should be just fine, I left some minors.
x-pack/elastic-agent/README.md
Outdated
|
|
||
| #### Prerequisites | ||
| - create kubernetes cluster using kind, check [here](https://github.com/elastic/beats/blob/master/metricbeat/module/kubernetes/_meta/test/docs/README.md) for details | ||
| - deploy kube-state-metrics |
There was a problem hiding this comment.
4f18959
this is a link to the metricbeat Readme to not repeat the same steps multiple times, maybe it could be moved to "common" how-to later
x-pack/elastic-agent/README.md
Outdated
| #### Prerequisites | ||
| - create kubernetes cluster using kind, check [here](https://github.com/elastic/beats/blob/master/metricbeat/module/kubernetes/_meta/test/docs/README.md) for details | ||
| - deploy kube-state-metrics | ||
| - deploy ELK stack or use [elastic cloud](https://cloud.elastic.co), check [here](https://github.com/elastic/beats/blob/master/metricbeat/module/kubernetes/_meta/test/docs/README.md) for details |
There was a problem hiding this comment.
Well it depends on if we what standalone or managed mode. With standalone we only need an ES running and it can be on cloud or locally (on same k8s cluster). With managed mode though is not so easy to have a local setup which would mean that we would have ES+Kibana+FleetServer+Registry running locally. At the moment I'm not so sure how easy it is but for sure we don't have a ready to use example for this.
There was a problem hiding this comment.
I've seen k8s manifests for ES+Kibana+FleetServer+Registry here -
https://github.com/elastic/e2e-testing/tree/master/cli/config/kubernetes/base, might be smth to check later
x-pack/elastic-agent/README.md
Outdated
| - download all-in-ome manifest: | ||
| ``` | ||
| ELASTIC_AGENT_VERSION="8.0" | ||
| curl -L -O https://raw.githubusercontent.com/elastic/beats/${ELASTIC_AGENT_VERSION}/deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml |
There was a problem hiding this comment.
Ok, so it looks like we focus on standalone mode only. It's just fine if we mention it in the tittle of this section :).
There was a problem hiding this comment.
Why should it be specific for standalone or managed? We can provide both options. The most important is to mention the update in the image name and imagePullPolicy. For the env variables I believe it is not in the scope of these instructions as we don't know which way the user has deployed the stack (elastic package or cloud or something else). A mention to which env vars to update depending if it is standalone or managed would be adequate I believe. @ChrsMark, @tetianakravchenko what do you think?
There was a problem hiding this comment.
@MichaelKatsoulis sorry, I somehow missed your question. Initially I've tried to run this locally (local ES+Kibana) with standalone elastic-agent as I was not sure how to run it locally in managed mode. I see your point and will adjust instructions to make them more generic.
There was a problem hiding this comment.
@ChrsMark @MichaelKatsoulis could you please give another look to this PR?
…e mode on Kubernetes' Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
|
Pinging @elastic/integrations (Team:Integrations) |
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
Signed-off-by: Tetiana Kravchenko tetiana.kravchenko@elastic.co
What does this PR do?
This PR adds instructions on how to test elastic agent on Kubernetes locally.
Why is it important?
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs