TDengine-IDMP Helm Chart

This Helm Chart deploys the TDengine Industrial Data Management Platform service on Kubernetes.

Prerequisites

helm install tdengine-idmp .

Or with custom values:

helm install tdengine-idmp . -f my-values.yaml

helm uninstall tdengine-idmp

The following table lists the configurable parameters of the chart and their default values.

Parameter	Description	Default
`replicaCount`	Number of replicas	`1`
`image.repository`	Image repository	`tdengine/idmp-ee`
`image.tag`	Image tag	`latest`
`image.pullPolicy`	Image pull policy	`IfNotPresent`
`service.type`	Kubernetes service type	`ClusterIP`
`service.port`	Service port	`6042`
`resources`	Resource requests and limits	`{}`
`persistence.enabled`	Enable persistent storage	`false`
`persistence.size`	Persistent volume size	`2Gi`
`persistence.storageClass`	StorageClass for persistent volume	`""`
`nodeSelector`	Node selector for pod assignment	`{}`
`tolerations`	Tolerations for pod assignment	`[]`
`affinity`	Affinity rules for pod assignment	`{}`

You can override any parameter using --set key=value or by editing values.yaml.

ClusterIP (default): Use port-forward to access from your local machine:
```
kubectl port-forward svc/tdengine-idmp 6042:6042 --address 0.0.0.0
```
Then access localhost:6042.
NodePort:
1. Get the NodePort and node IP:
```
kubectl get svc tdengine-idmp
kubectl get nodes -o wide
```
2. Access the service at http://<NodeIP>:<NodePort>
  Note:
  - Make sure the NodePort is open in your firewall or cloud security group.
  - You can use any node's IP in the cluster.
LoadBalancer: Access via the external IP assigned by your cloud provider.

To enable persistent storage, set persistence.enabled: true in values.yaml. Make sure your cluster supports PersistentVolume provisioning.

You can customize the deployment by editing values.yaml or using --set on the command line.