[DevOps] adding readme for how to deploy elasticstack using helm charts

[fxdgear]

Link to issue

• Related: Create Observability Stack for Monitoring and Logging #3

Changelog entry

• README on how to use helm to install elastic stack into an elastic-stack namespace in a k8s cluster.

Additional info

This has been deployed already for testing into the test-es namespace on preprod. This namespace can be deleted at anytime.

I'd suggest a review of the available overrides for each helmchart to ensure that the right settings are getting set that meet the needs for this project.

The default settings have been applied to each service in the Elastic Stack so far and that means:

• metricbeat is pulling metric data from all pods in all namespaces
• filebeat is pulling all logs from all pods in all namespaces
• kibana is running without an ingress, which means you need to configure port forwarding to access kibana
• elasticsearch has no default username/password (also there is no ingress so you must have port forwarding enabled to access elasticsearch).
• AMP server is configured to connect to elasticsearch, but no data is being shipped to APM server yet. This is something that the CHIME app would need to be updated to support.

---

Pull Request Checklist

For Reviewer

• Submitted under the correct tag
• Runs without error or warning
• Documentation revised / included
• Unit tests included
• Issues referenced
• Does not create new bugs / issues

[MooseQuest]

For APM an issue has been opened to track #566

[MooseQuest]

This looks good to me. This is enough of a readme to get started.

[lottspot]

I think it's more appropriate if we file this information under docs/. Maybe docs/helm or something like that.

[lottspot]

Er... make that docs/operations/helm

[fxdgear]

I think it's more appropriate if we file this information under docs/. Maybe docs/helm or something like that.

Moving to Docs makes sense.

I was hoping that this README would live next to the customized values yaml files.

BUT maybe this does make more sense in the docs directory and a more terse readme can live here, and reference the docs directory.

[lottspot]

@fxdgear We have generally been keeping documentation in docs/operations/ and operational files under k8s/

[fxdgear]

@lottspot PTAL. I've updated the locations of files as well as updated the README to reference the new locations.

[lottspot]

Looks good!