Snipeit-IT is free open source IT asset/license management system

In order for Snipe-IT to work correctly you need to set the yaml-key config.snipeit.key in the values.yaml. This must be a Base64 Encoded key, which you have to set before deploying this Chart.

$ docker run -i -t snipe/snipe-it php artisan key:generate --show

Then set the generated key from the output with --set config.snipeit.key when you're deploying.

$ helm repo add t3n https://storage.googleapis.com/t3n-helm-charts
$ helm install t3n/snipeit --set config.snipeit.key="base64:....."

This chart bootstraps a Snipe-IT deployment on a Kubernetes cluster using the Helm package manager.

To install the chart with the release name my-release:

$ helm install --name my-release t3n/snipeit --set config.snipeit.key="base64:....."

The command deploys Snipe-IT on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Tip: List all releases using helm list

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

The following table lists the configurable parameters of the Snipe-IT chart and their default values.

$ helm install --name my-release \
  --set service.type=LoadBalancer \
    t3n/snipeit

The above command sets the service type LoadBalancer.

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml t3n/snipeit

Tip: You can use the default values.yaml

The Snipe-IT image stores persistence under /var/lib/snipeit path of the container. A dynamically managed Persistent Volume Claim is used to keep the data across deployments, by default. This is known to work in GCE, AWS, and minikube. Alternatively, a previously configured Persistent Volume Claim can be used.

1. Create the PersistentVolume
2. Create the PersistentVolumeClaim
3. Install the chart

$ helm install --name my-release \
    --set persistence.existingClaim=PVC_NAME \
    t3n/snipeit

Snipe-IT uses .env file to store configuration variables. This includes Email configuration, advanced configurations like proxy, login throttling etc. To override the default values for these variables, use the config.snipeit.envConfig.

config:
  snipeit:
    envConfig:
      MAIL_HOST: smtp.example.com
      MAIL_PORT: 25
      MAIL_USERNAME: username
      MAIL_PASSWORD: password
      MAIL_FROM_ADDR: snipeit@example.com
      MAIL_FROM_NAME: Snipe-IT

To use manually created secrets for the database configuration, use the config.externalSecret. You can create a secret with the following command:

kubectl create secret generic my-db-secret \
  --from-literal=MYSQL_USER=<your_mysql_user> \
  --from-literal=MYSQL_DATABASE=<your_mysql_database> \
  --from-literal=MYSQL_PASSWORD=<your_mysql_password> \
  --from-literal=MYSQL_PORT_3306_TCP_ADDR=<your_mysql_host> \
  --from-literal=MYSQL_PORT_3306_TCP_PORT=<your_mysql_port> \
  --from-literal=APP_KEY=<your_app_key>

It is possible to add additional manifests into a deployment, to extend the chart. One of the reason is to deploy a manifest specific to a cloud provider ( BackendConfig on GKE for example ).

extraManifests:
  - apiVersion: cloud.google.com/v1beta1
    kind: BackendConfig
    metadata:
      name: "{{ .Release.Name }}-test"
    spec:
      securityPolicy:
        name: "gcp-cloud-armor-policy-test"