Skip to main content

Installing Ignition

Ignition Helm Chart Defaults​

Installing the Ignition Helm Chart with the default values will result in the following:

  • Ignition Standalone Gateway in a single-pod StatefulSet.
  • Data volume provisioned from the default storage class of size 3Gi.
  • Headless ClusterIP Service resource with ports 8088/tcp, 8043/tcp and 8060/tcp.
  • Ingress resource using the default Ingress class with an http rule.
  • No TLS enabled by default.
  • Resource limits applied at 1 CPU and 1.5Gi RAM with 75% JVM Heap Percentage.
  • Gateway Admin initial password stored as a Secret resource.

Upon installation, you'll be presented with some notes that will help you get started:

$ helm install ignition inductiveautomation/ignition
NAME: ignition
LAST DEPLOYED: Thu Sep 11 18:42:53 2025
NAMESPACE: demo
STATUS: deployed
REVISION: 1
NOTES:
🎉 Thank you for installing Ignition 8.3.0 by Inductive Automation!

🚀 Ignition Gateway is reachable at:
  - http://ignition.localtest.me

🔐 The initial Ignition Gateway `admin` password can be retrieved with:

  kubectl get secret -n demo ignition-gateway-admin-password --template='{{ printf "%s\n" (index .data "gateway-admin-password" | base64decode) }}'

To learn more about Ignition, please visit our website at https://inductiveautomation.com

Once the pod's readiness probe validates, you'll see the edition selection screen at the gateway URL.

Auto-Commissioning​

You can automate the commissioning process by specifying commissioning values. Using the testing.yaml values file below will have Ignition perform a full startup of standard edition and implied acceptance of the Ignition EULA.

# testing.yaml
commissioning:
  edition: "standard"
  acceptIgnitionEULA: true
  disableQuickstart: true

After creating your values override file, upgrade your release (named "ignition") with:

helm upgrade --install ignition inductiveautomation/ignition --values testing.yaml

Setting a static initial admin password​

There are a couple of ways you can customize the initial Ignition "admin" password:

  1. Default of a randomly generated password stored in a Secret resource.
  2. Referencing an existing opaque Secret resource with a gateway-admin-password key and associated value.
  3. Setting the GATEWAY_ADMIN_PASSWORD environment variable in your Helm value overrides.

Each method will result in a Secret resource with the specified password that can be read by those with appropriate permissions.

Option 3 can be helpful for testing; however, it isn't recommended to store secrets in Helm values files (which are typically committed to source control). Here is an example that you can use during your exploration:

# testing.yaml
commissioning:
  edition: "standard"
  acceptIgnitionEULA: true
  disableQuickstart: true

gateway:
  env:
    GATEWAY_ADMIN_PASSWORD: "super-secret-password"