This repo provides an implementation of a strongDM Client Container inside Kubernetes using Helm.
Learn more about deploying strongDM's cliet container inside Kubernetes on our docs site.
-
A Kubernetes Cluster v1.16+
-
Helm 3.0+
-
Git
-
If you are going to use Nginx Ingress Controller, then you will need to manually patch your services to allow TCP and UDP traffic
helm repo add strongdm https://helm.strongdm.com/stable/
helm install [RELEASE_NAME] strongdm/sdm-client -f values.yaml
helm status [RELEASE_NAME]See configuration below.
See helm install for command documentation.
helm upgrade [RELEASE_NAME] strongdm/sdm-client --installSee helm upgrade for command documentation.
helm uninstall [RELEASE_NAME]The command removes all the Kubernetes components associated with the release and deletes the release.
See helm uninstall for command documentation.
The following table lists the configurable parameters of the strongDM relay/gateway chart and their default values.
| Parameter | Description | Default | Required |
|---|---|---|---|
| .global.service.type | The kind of service you'd like to run for the gateway. E.G. ClusterIP or Loadbalancer |
ClusterIP |
☐ |
| .global.secret.token | The base64 encoded value of the relay or gateway token generated in the Admin UI. |
None | ☑ |
| .global.deployment.replicas | The number of container replicas you'd like to run for the deployment. | 1 | ☐ |
| .global.deployment.repository | The image you'd like to use for the strongDM client. | public.ecr.aws/strongdm/client | ☑ |
| .global.deployment.tag | The tag for the image you'd like to use for the strongDM client. | latest | ☑ |
| .global.deployment.imagePullPolicy | The policy for pulling a new image from the repo. | Always | ☑ |
| .global.deployment.ports | A list of ports you'd like to have the service listening on. The ports will coincide with the SDM port you are exposing from SDM. | None | ☐ |
| .configmap.SDM_DOCKERIZED | Setting this will automatically send logs to STDOUT overriding settings in AdminUI. | true | ☐ |