Skip to content
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

feat: Elastic Agent Standalone Helm Chart #28103

Conversation

kuisathaverat
Copy link
Contributor

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

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

Tested with kind

git clone git@github.com:kuisathaverat/beats.git
cd beats/deploy/kubernetes/helm-charts/elastic_agent
kind create cluster
kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/deploy/local-path-storage.yaml
helm repo add elastic https://helm.elastic.co
helm install elasticsearch elastic/elasticsearch --set "imageTag=7.15.0,esJavaOpts='-Xmx1g -Xms1g',antiAffinity=soft,replicas=1,minimumMasterNodes=1" 
helm install kibana  elastic/kibana --set "imageTag=7.15.0"

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 install fleet-server ./ --values helm-values-fleet-server.yml
helm install elastic-agent ./  --values helm-values.yml

helm-values.yml


helm-values-fleet-server.yml



Related issues

Use cases

@kuisathaverat kuisathaverat added enhancement Team:Automation Label for the Observability productivity team backport-skip Skip notification from the automated backport with mergify labels Sep 23, 2021
@kuisathaverat kuisathaverat self-assigned this Sep 23, 2021
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Sep 23, 2021
@elasticmachine
Copy link
Collaborator

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-09-23T17:26:57.098+0000

  • Duration: 11 min 25 sec

  • Commit: c4d5e4d

Steps errors 2

Expand to view the steps failures

make check-default
  • Took 1 min 10 sec . View more details here
  • Description: make check-default
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 2'

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

@kuisathaverat
Copy link
Contributor Author

I will make a new PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify enhancement Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants