|
1 | | -# helm-charts |
2 | | -Helm Charts for HyperDX OSS V2 |
| 1 | +# HyperDX V2 Helm Charts |
| 2 | + |
| 3 | +Welcome to the official HyperDX Helm charts repository. This guide provides instructions on how to install, configure, and manage your HyperDX V2 deployment using Helm. |
| 4 | + |
| 5 | +## Prerequisites |
| 6 | + |
| 7 | +- [Helm](https://helm.sh/) v3+ |
| 8 | +- Kubernetes cluster (v1.20+ recommended) |
| 9 | +- `kubectl` configured to interact with your cluster |
| 10 | + |
| 11 | +## Adding the HyperDX Helm Repository |
| 12 | + |
| 13 | +First, add the HyperDX Helm repository: |
| 14 | + |
| 15 | +```sh |
| 16 | +helm repo add hyperdx https://hyperdxio.github.io/helm-charts |
| 17 | +helm repo update |
| 18 | +``` |
| 19 | + |
| 20 | +## Installing HyperDX |
| 21 | + |
| 22 | +To install the HyperDX chart with default values: |
| 23 | + |
| 24 | +```sh |
| 25 | +helm install my-hyperdx hyperdx/hdx-oss-v2 |
| 26 | +``` |
| 27 | + |
| 28 | +You can customize settings by editing `values.yaml` or using `--set` flags. |
| 29 | + |
| 30 | +```sh |
| 31 | +helm install my-hyperdx hyperdx/hdx-oss-v2 -f values.yaml |
| 32 | +``` |
| 33 | + |
| 34 | +or |
| 35 | + |
| 36 | +```sh |
| 37 | +helm install my-hyperdx hyperdx/hdx-oss-v2 --set key=value |
| 38 | +``` |
| 39 | + |
| 40 | +To retrieve the default values: |
| 41 | + |
| 42 | +```sh |
| 43 | +helm show values hyperdx/hdx-oss-v2 > values.yaml |
| 44 | +``` |
| 45 | + |
| 46 | +### Example Configuration |
| 47 | + |
| 48 | +```yaml |
| 49 | +replicaCount: 2 |
| 50 | +resources: |
| 51 | + limits: |
| 52 | + cpu: 500m |
| 53 | + memory: 512Mi |
| 54 | + requests: |
| 55 | + cpu: 250m |
| 56 | + memory: 256Mi |
| 57 | +ingress: |
| 58 | + enabled: true |
| 59 | + annotations: |
| 60 | + kubernetes.io/ingress.class: nginx |
| 61 | + hosts: |
| 62 | + - host: hyperdx.example.com |
| 63 | + paths: |
| 64 | + - path: / |
| 65 | + pathType: ImplementationSpecific |
| 66 | +``` |
| 67 | +
|
| 68 | +## Using Secrets |
| 69 | +
|
| 70 | +For handling sensitive data such as API keys or database credentials, use Kubernetes secrets. The HyperDX Helm charts provide default secret files that you can modify and apply to your cluster. |
| 71 | +
|
| 72 | +### Using Pre-Configured Secrets |
| 73 | +
|
| 74 | +The Helm chart includes a default secret template located at [`charts/hdx-oss-v2/templates/secrets.yaml`](https://github.com/hyperdxio/helm-charts/blob/main/charts/hdx-oss-v2/templates/secrets.yaml). This file provides a base structure for managing secrets. |
| 75 | + |
| 76 | + |
| 77 | +If you need to manually apply a secret, modify and apply the provided `secrets.yaml` template: |
| 78 | + |
| 79 | +```yaml |
| 80 | +apiVersion: v1 |
| 81 | +kind: Secret |
| 82 | +metadata: |
| 83 | + name: hyperdx-secret |
| 84 | + annotations: |
| 85 | + "helm.sh/resource-policy": keep |
| 86 | +type: Opaque |
| 87 | +data: |
| 88 | + API_KEY: <base64-encoded-api-key> |
| 89 | +``` |
| 90 | + |
| 91 | +Apply the secret to your cluster: |
| 92 | + |
| 93 | +```sh |
| 94 | +kubectl apply -f secrets.yaml |
| 95 | +``` |
| 96 | + |
| 97 | +### Creating a Custom Secret |
| 98 | + |
| 99 | +If you prefer, you can create a custom Kubernetes secret manually: |
| 100 | + |
| 101 | +```sh |
| 102 | +kubectl create secret generic hyperdx-secret \ |
| 103 | + --from-literal=API_KEY=my-secret-api-key |
| 104 | +``` |
| 105 | + |
| 106 | +### Referencing a Secret in `values.yaml` |
| 107 | + |
| 108 | +```yaml |
| 109 | +hyperdx: |
| 110 | + apiKey: |
| 111 | + valueFrom: |
| 112 | + secretKeyRef: |
| 113 | + name: hyperdx-secret |
| 114 | + key: API_KEY |
| 115 | +``` |
| 116 | + |
| 117 | +## Upgrading the Chart |
| 118 | + |
| 119 | +To upgrade to a newer version: |
| 120 | + |
| 121 | +```sh |
| 122 | +helm upgrade my-hyperdx hyperdx/hdx-oss-v2 -f values.yaml |
| 123 | +``` |
| 124 | + |
| 125 | +To check available chart versions: |
| 126 | + |
| 127 | +```sh |
| 128 | +helm search repo hyperdx |
| 129 | +``` |
| 130 | + |
| 131 | +## Uninstalling HyperDX |
| 132 | + |
| 133 | +To remove the deployment: |
| 134 | + |
| 135 | +```sh |
| 136 | +helm uninstall my-hyperdx |
| 137 | +``` |
| 138 | + |
| 139 | +This will remove all resources associated with the release, but persistent data (if any) may remain. |
| 140 | + |
| 141 | +## Troubleshooting |
| 142 | + |
| 143 | +### Checking Logs |
| 144 | + |
| 145 | +```sh |
| 146 | +kubectl logs -l app.kubernetes.io/name=hdx-oss-v2 |
| 147 | +``` |
| 148 | + |
| 149 | +### Debugging a Failed Install |
| 150 | + |
| 151 | +```sh |
| 152 | +helm install my-hyperdx hyperdx/hdx-oss-v2 --debug --dry-run |
| 153 | +``` |
| 154 | + |
| 155 | +### Verifying Deployment |
| 156 | + |
| 157 | +```sh |
| 158 | +kubectl get pods -l app.kubernetes.io/name=hdx-oss-v2 |
| 159 | +``` |
| 160 | + |
| 161 | +For more details, refer to the [Helm documentation](https://helm.sh/docs/) or open an issue in this repository. |
| 162 | + |
| 163 | +--- |
| 164 | + |
| 165 | +## Contributing |
| 166 | + |
| 167 | +We welcome contributions! Please open an issue or submit a pull request if you have improvements or feature requests. |
| 168 | + |
| 169 | +## License |
| 170 | + |
| 171 | +This project is licensed under the [MIT License](LICENSE). |
3 | 172 |
|
4 | | -WIP |
|
0 commit comments