Closed aaadipop closed 3 months ago
I found this answer but idk how to add it to fleet config
I found this answer but idk how to add it to fleet config
This is because in Fleet mode the configuration is centralized and defined in the Kibana config. I think you have to update the Fleet server policy to include this custom configuration. Could you please open a thread in https://discuss.elastic.co/c/elastic-stack/elastic-agent/91 to ask how this custom configuration can be included in the xpack.fleet.agentPolicies
section of your Kibana resource?
I'm closing this issue as it seems to be a question about the Fleet server configuration, feel free to reopen if you think there is a bug in ECK or if you think something is missing in the Helm chart.
Thanks
Bug Report
What did you do? Install two eck-stack in two different namespaces, first one works as expected, the second one have the following error
What did you expect to see? working eck stack
What did you see instead? Under which circumstances?
Error: could not start the HTTP server for the API: listen tcp 127.0.0.1:6791: bind: address already in use
error ineck-stack-eck-agent-agent
Environment AWS EKS
helm chart version = "0.4.0"
Kubernetes information: EKS
Resource definition:
Logs: