Installing Gremlin on Kubernetes with Helm
The Gremlin Helm Chart is the recommended way to install the Gremlin Agent on Kubernetes. If you want to install Gremlin using just <span class="code-class-custom">kubectl</span> and pure YAML, see Install Gremlin on Kubernetes manually.
The steps for deploying to Kubernetes with Helm are:
Gather your credentials
All Gremlin integration installations require you to use one of Gremlin's authentication methods. With Helm, you can use either signature (i.e. certificate)-based authentication or secret authentication. Secret-based authentication is easier to implement, but we recommend using certificate-based authentication. We'll show both methods in this guide.
First, retrieve your Team ID from your team settings page. Next, if you're using secret-based authentication, create a new secret, copy the secret to a text file (or keep the pop-up open), then continue to the next step.
If you're using certificate-based authentication, generate a new certificate pair, or download an existing certificate pair if one exists. Unzip the folder containing your certificates, then continue to the next step.
Deploy the Helm chart
Now that we have our credentials, let's add the Gremlin Helm repo and create a new namespace for our deployment:
Now we'll deploy the Chart. With this command, your team ID and secrets/certificates are passed directly to the Helm Chart. If you'd prefer to manage these secrets outside of Helm, see our Helm Chart documentation.
For secret-based authentication:
For certificate-based authentication:
The Helm Chart includes several additional options for customizing to your environment. These options include:
- Specifying a container driver (Gremlin will try to auto-detect the current driver, but you can also tell Gremlin to use a specific driver).
- Enabling Gremlin on the Kubernetes Master so you can run tests on the Kubernetes Control Plane.
- Enabling AppArmor support for clusters that use AppArmor.
- Installing Gremlin's custom PodSecurityPolicy or seccomp policy for restrictive clusters.
- Configuring Gremlin to use a proxy.
- Allowing multiple Gremlin teams to target specific namespaces.
- Allow adding arbitrary environment variables.
- Allow adding arbitrary annotations to Kubernetes service account.
These are optional and are only necessary if Gremlin doesn't run using the default options. To learn more, see the Additional Configuration for Helm docs.
Verify your installation
On the cluster, you can run the following command to check that the Gremlin Agent was installed properly:
This should list one Gremlin Agent for each node in your cluster, plus one Pod named <span class="code-class-custom">chao</span>. For example, this is the output for a three-node cluster:
The following example shows 2 pending pods, which means the installation is incomplete. Contact your cluster administrator to debug why Gremlin is unable to run on those nodes.
If you need additional troubleshooting help, see Gremlin Agent in the Gremlin Knowledge Base.
Uninstalling Gremlin from Kubernetes with Helm
To uninstall Gremlin via Helm, run the following commands: