This Helm chart repository enables you to install a ENBUILD
Helm chart directly from it into your Kubernetes cluster. Please refer to the
ENBUILD documentation for all
the additional details required.
# Let helm the command line tool know about a Helm chart repository# that we decide to name enbuild.
❯ helm repo add vivsoft https://vivsoftorg.github.io/enbuild
# Update the Helm chart repository.
❯ helm repo update vivsoft
# Search for the ENBUILD Helm chart in the enbuild Helm chart repository.
❯ helm search repo vivsoft/enbuild
NAME CHART VERSION APP VERSION DESCRIPTION
vivsoft/enbuild 0.0.7 1.0.6 A Helm chart for ENBUILD
# Simplified example on how to install a Helm chart from a Helm chart repository# named vivsoft in a namespace named enbuild. See the Helm chart's documentation for additional details# required.
❯ helm upgrade --install enbuild vivsoft/enbuild --namespace enbuild --create-namespace
# To install a specific version of the Helm chart.
❯ helm upgrade --install enbuild vivsoft/enbuild --namespace enbuild --create-namespace --version 0.0.1
Uninstalling the Chart
To uninstall/delete the enbuild deployment:
❯ helm delete --namespace enbuild enbuild
Parameters
Global parameters
Name
Description
Value
global.AppVersion
[default: ""] Provide custom appVersion, to override the default one. All the ENBUILD images will be of the same version. To use indidual tag for each service set the tag on per service basis.
""
global.domain
What domain to use to expose the ENBUILD using istio or Ingress
ijuned.com
global.disable_tls_gitlab
Set to true if you are using self-signed certificates
false
global.ingress.enabled
Should we create the Ingress Resources ?
false
global.ingress.tls
Is Ingress TLS enabled ?
false
global.ingress.tls_secret
If Ingress is TLS enabled, Provide the Secret for the TLS Certificate.
""
global.ingress.classname
Ingress classname if enabled.
""
global.ingress.annotations
Ingress annotations if enabled.
[]
global.istio.enabled
Should we create the Istio Resources ?
false
global.istio.gateway
Istio gateway to use for creating Virtual Service.
istio-system/main
Container Registry Parameters
Name
Description
Value
imageCredentials
Should we use a private container registry? if yes provide the following parameters
{}
imageCredentials.registry
Container registry Path
""
imageCredentials.username
Container registry Username
""
imageCredentials.password
Container registry password
""
Jupyterhub Parameters
Name
Description
Value
jupyterhub.cull.enabled
Deploy Jupyterhub
false
ENBUILD RabbitMQ parameters
Name
Description
Value
rabbitmq.enabled
Set to false to use existing RabbitMQ
true
rabbitmq.replicaCount
RabbitMQ replicaCount
1
rabbitmq.auth.username
RabbitMQ username
admin
rabbitmq.auth.password
RabbitMQ password
SuperSecret
rabbitmq.auth.erlangCookie
RabbitMQ erlangCookie
lamba
rabbitmq.host
If rabbitmq.enabled is false , provide the right rabbitmq endpoint
""
rabbitmq.queue_prefix
Queue Prefix for all RabbitMQ Queues
enbuild
ENBUILD Backend/DB parameters
Name
Description
Value
mongodb.enabled
Set to true to Deploy the MongoDB.
false
mongodb.mongo_root_username
DB username. If mongodb.enabled this is used to to set the username. Else this is username for existing Cosmos or DocumentDB
""
mongodb.mongo_root_password
DB Password. If mongodb.enabled this is used to to set the password. Else this is password for existing Cosmos or DocumentDB
""
mongodb.mongo_server
If mongodb.enabled is false , provide the right cosmosDB/DocumentDB endpoint