feat: Elastic Agent Standalone Helm Chart #28103
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It adds a Helm chart deployment for the Elastic Agent in the deployments folder.
Why is it important?
Helm charts are a common way to make deployments in Kubernetes.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Tested with kind
After Elasticsearch and Kibana are up and running, you will install the Fleet Server.
To configure the Fleet Server you need to get the FLEET_SERVER_SERVICE_TOKEN from kibana fleet section,
then update the helm-values-fleet-server.yml file,
finally run the following command.
helm-values.yml
helm-values-fleet-server.yml
Related issues
Use cases