Reference

Gimlet Agent configuration reference

On this page you can see the deployment manifests of the Gimlet Agent.

You can use these manifests to install the agent. Alternatively, you can install the agent through Gimlet Stack.

ServiceAccount and ClusterRole

apiVersion: v1
kind: ServiceAccount
metadata:
  name: gimlet-agent
  namespace: gimlet
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: gimlet-agent
subjects:
  - kind: ServiceAccount
    name: gimlet-agent
    namespace: gimlet
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io

Agent installation

Use the following Helm template command to get the installation manifests.

cat << EOF > values.yaml
image:
  repository: ghcr.io/gimlet-io/gimlet-dashboard
  tag: agent-latest
  pullPolicy: Always
serviceAccount: gimlet-agent
EOF


helm repo add onechart https://chart.onechart.dev
helm template gimlet-agent onechart/onechart -f values.yaml

Configuring the agent

image:
  repository: ghcr.io/gimlet-io/gimlet-dashboard
  tag: agent-latest
  pullPolicy: Always
serviceAccount: gimlet-agent
+vars:
+  HOST: gimletd.mycompany.com
+  AGENT_KEY: xyz
+  ENV: staging

where:

  • HOST is where you run Gimlet Dash
  • AGENT_KEY is the api key for agents. Find it in Gimlet Dash's startup log
  • ENV is the name of the environment like staging or production. If you run environments in namespaces, use the <env>=<namespace> format.

Limiting resources

cat << EOF > values.yaml
image:
  repository: ghcr.io/gimlet-io/gimlet-dashboard
  tag: agent-latest
  pullPolicy: Always
serviceAccount: gimlet-agent
+resources:
+  requests:
+    cpu: "50m"
+    memory: "100Mi"
+  limits:
+    cpu: "500m"
+    memory: "200Mi"
EOF


helm template gimlet-agent onechart/onechart -f values.yaml
Previous
Gimletd configuration reference