|
| 1 | +# Sumo Logic Helm Chart |
| 2 | +| DISCLAIMER | |
| 3 | +| --- | |
| 4 | +| This Helm chart is still under development. | |
| 5 | + |
| 6 | +## Introduction |
| 7 | + |
| 8 | +This chart deploys Kubernetes resources for collecting Kubernetes logs, metrics, and events; enriching them with deployment, pod, and service level metadata; and sending them to Sumo Logic. |
| 9 | + |
| 10 | +## Prerequisite |
| 11 | + |
| 12 | +Before installing the chart, you'll need to run the provided `setup.sh` script. It will create a namespace called `sumologic` and a secret with the same name that contains the Sumo Logic collection endpoints. |
| 13 | + |
| 14 | +To run the script that creates the namespace and secret, use the following command: |
| 15 | + |
| 16 | +```bash |
| 17 | +curl -s https://raw.githubusercontent.com/SumoLogic/sumologic-kubernetes-collection/master/deploy/kubernetes/setup.sh \ |
| 18 | + | bash -s - -d false -y false <api_endpoint> <access_id> <access_key> |
| 19 | +``` |
| 20 | +NOTE: You'll need to set `-d` and `-y` to false so the script does not download the YAML file or deploy the resources into your cluster yet. Details on the parameters are explained [here](https://github.com/SumoLogic/sumologic-kubernetes-collection/tree/master/deploy#automatic-source-creation-and-setup-script). |
| 21 | + |
| 22 | +_Soon this step will not be needed after we move the collection setup into a helm hook. Stay tuned._ |
| 23 | + |
| 24 | +## Installing the Chart |
| 25 | + |
| 26 | +To install the chart, first add the `sumologic` private repo: |
| 27 | + |
| 28 | +```bash |
| 29 | +helm repo add sumologic https://sumologic.github.io/sumologic-kubernetes-collection |
| 30 | +``` |
| 31 | + |
| 32 | +Install the chart with release name `collection` and namespace `sumologic` |
| 33 | +```bash |
| 34 | +helm install sumologic/sumologic --name collection --namespace sumologic |
| 35 | +``` |
| 36 | + |
| 37 | +NOTE: If you install the chart with a different release name or a different namespace, you will need to override remote write URLs for Prometheus and the host for fluent-bit. We recommend using an override file due to the number of URLs that need to be overridden. You can use the following command to download the override file and replace the `<RELEASE-NAME>` and `<NAMESPACE>`: |
| 38 | + |
| 39 | +```bash |
| 40 | +curl https://raw.githubusercontent.com/SumoLogic/sumologic-kubernetes-collection/master/deploy/helm/sumologic/values.yaml | \ |
| 41 | +sed 's/\collection-sumologic.sumologic'"/<RELEASE-NAME>-sumologic.<NAMESPACE>/g" > values.yaml |
| 42 | +``` |
| 43 | + |
| 44 | +For example, if your release name is `my-release` and namespace is `my-namespace`: |
| 45 | +```bash |
| 46 | +curl https://raw.githubusercontent.com/SumoLogic/sumologic-kubernetes-collection/master/deploy/helm/sumologic/values.yaml | \ |
| 47 | +sed 's/\collection-sumologic.sumologic'"/my-release-sumologic.my-namespace/g" > values.yaml |
| 48 | +``` |
| 49 | + |
| 50 | +Then, install the chart with the override file. |
| 51 | +```bash |
| 52 | +helm install sumologic/sumologic --name my-release --namespace my-namespace -f values.yaml |
| 53 | +``` |
| 54 | + |
| 55 | + |
| 56 | +> **Tip**: List all releases using `helm list`, a release is a name used to track a specific deployment |
| 57 | +
|
| 58 | +## Uninstalling the Chart |
| 59 | + |
| 60 | +To uninstall/delete the `collection` release: |
| 61 | + |
| 62 | +```bash |
| 63 | +helm delete collection |
| 64 | +``` |
| 65 | +> **Tip**: Use helm delete --purge collection to completely remove the release from Helm internal storage |
| 66 | +
|
| 67 | +The command removes all the Kubernetes components associated with the chart and deletes the release. |
0 commit comments