Installation YAMLs and Helm chart

cat << EOF > values.yaml
image:
  repository: ghcr.io/gimlet-io/gimletd
  tag: latest
containerPort: 8888
probe:
  enabled: true
  path: /
EOF

helm template gimletd onechart/onechart -f values.yaml

Volume to back the state

cat << EOF > values.yaml
image:
  repository: ghcr.io/gimlet-io/gimletd
  tag: latest
probe:
  enabled: true
  path: /
+volumes:
+  - name: data
+    path: /var/lib/gimletd
+    size: 10Gi
+    storageClass: default
EOF

helm template gimletd onechart/onechart -f values.yaml

Ingress

cat << EOF > values.yaml
image:
  repository: ghcr.io/gimlet-io/gimletd
  tag: latest
probe:
  enabled: true
  path: /
+ingress:
+  annotations:
+    kubernetes.io/ingress.class: nginx
+    cert-manager.io/cluster-issuer: letsencrypt
+  host: gimletd.mycompany.com
+  tlsEnabled: true
EOF

helm template gimletd onechart/onechart -f values.yaml

Debug sidecar container

cat << EOF > values.yaml
image:
  repository: ghcr.io/gimlet-io/gimletd
  tag: latest
probe:
  enabled: true
  path: /
+debugSidecarEnabled: true
EOF

helm template gimletd onechart/onechart -f values.yaml

Limiting resources

cat << EOF > values.yaml
image:
  repository: ghcr.io/gimlet-io/gimletd
  tag: latest
probe:
  enabled: true
  path: /
+resources:
+  requests:
+    cpu: "50m"
+    memory: "200Mi"
+  limits:
+    cpu: "2000m"
+    memory: "1000Mi"
EOF

helm template gimletd onechart/onechart -f values.yaml

Next steps

• Continue with configuring GimletD
• Or see how to create release artifacts directly with Gimlet CLI, or with Gimlet's CircleCI integration
• See how to create ad-hoc or policy based releases