Platform release - v22.38
Description of HELM3 common configuration values for all environments and their purpose.
This document describes the HELM3 deployment parameters and their descriptions which are common for all environments. Check the general description for explanations and specifications for different environments.
Here are the configurations divided into sections.
22.38 - The format is year (YY
) and week (WW
) added with an extra optional release (V
).
app
- Kubernetes configuration for assigning pods to the correct nodes.
GCP
by default. Supported values: AWS
, GCP
and AZURE
.
Container runtime used by the cloudProvider. Allowed values: containerd
, docker
Whether we should expose platform version for end-user. Will be displayed at least in frontend UI and API responses. Allowed values: true
, false
Allowed values: true
or false
. Enables deliveryMode
: 2
(persistent) for
all components on the installation which use supported sailor versions
(sailor-nodejs
from 2.7.0
and sailor-jvm
from 3.4.0
). Default value: false
.
"admiral-secrets"
- a separate secrets for the new replicated-admiral. Not used for now.
Secret containing main bulk of platform environment variables. Check the Platform environment secret section for more information.
Auto-generated secret for service discovery. It contains the internal URLs for the platform services.
This is the platform docker registry secret.
Secret containing an RSA private key. Check the Git-receiver secret section for more.
""
Secret used by the whole platform to pull platform microservice images from the dockerhub. Check the platform docker registry secret for details.
Platform uses this secret to push component docker container images to the docker registry. Check the docker registry push secret description for more information.
Platform uses this secret in the configuration of username/password authentication for internal docker registry. Check the Docker registry htpasswd secret description for more information.
clientKeySecretName
- Secret name with tls certificate and key. If specified,
will be mounted to the services and specified in the tlsCertificateKeyFile
connection option.
caSecretName
- Secret name with CA certificate to validate mongodb server
certificate in the client side. If specified, will be mounted to the services and
specified in the tlsCAFile
connection option.
Namespaces: You must create these namespaces in your Kubernetes cluster beforehand. HELM3 chart installations expect to find these namespaces during the installation of the platform version starting from the 21.31 release. Check namespaces page for More instructions.
"tasks"
Platform uses this namespace for pods running the integration flow steps. You can pick an arbitrary name but you must define it beforehand.
"platform"
Platform uses this namespace for the pods running the platform microservices.
"monitoring"
Platform uses this namespace for the pods running the monitoring microservices.
Service Apps: Links to charts for all microservices. Each app has a separate descriptors and charts pulled during the platform deployment. For more information check the platform microservices section.
"admiral"
"api"
"api-docs"
"bloody-gate"
"bran-read"
"bran-write"
"cache"
"default-backend"
"docker-registry"
"faceless-api"
"faceless-token-refresher"
"eio-fluentd"
"frontend"
"gendry"
"gitreceiver"
"gold-dragon-coin"
"handmaiden"
"ingress-nginx"
"iron-bank"
"knight-of-the-bloody-gate"
"lookout"
"maester"
"platform-storage-slugs"
"quota-service"
"raven"
"s3"
"scheduler"
"stakater-reloader"
"steward"
"webhooks"
"wiper"
Service availability: By default all services are enabled. You can disable any service by changing the value of enable parameter from true to false. However, we do not recommend doing this for system critical services. Consult the platform microservices section to know which services are critical.
enabled: true
name: "admiral-service"
enabled: true
name: "api-docs-service"
port: 8000
enabled: true
name: "api-service"
port: 9000
resources:
limits:
cpu: 3
requests:
cpu: 2
enabled: true
name: "bloody-gate-service"
port: 3000
enabled: true
name: "bran-read-service"
port: 5961
name: "bran-write-service"
enabled: true
enabled: true
name: "cache-service"
port: 6379
enabled: true
name: "default-backend-service"
port: 8080
enabled: true
name: "docker-registry-service"
storageDriver: "filesystem"
nodePort: 31000
loadBalancerIp: “”
path: "elasticio"
uri: ""
secured: false
enabled: true
name: "faceless-api-service"
port: 1396
enabled: true
name: "faceless-token-refresher-service"
port: 11396
enabled: true
name: "fluentd-service"
execGelfProto: ""
execGelfHost: ""
execGelfPort: ""
enabled: true
name: "frontend-service"
port: 8000
name: "gendry-service"
enabled: true
configMapName: "gendry-config"
enabled: true
name: "gitreceiver-service"
port: 4022
enabled: true
name: "gold-dragon-coin-service"
port: 9000
name: "handmaiden-service"
enabled: true
issuer:
name: letsencrypt-issuer
Available values: issuer/cluster-issuer
kind: issuer
enabled: true
error5xxUrl: ""
defaultBackendPort: ""
name: "ingress-loadbalancer"
httpPort: 80
httpsPort: 443
sshPort: 22
enabled: true
name: "iron-bank-service"
port: 3000
enabled: true
name: "knight-of-the-bloody-gate-service"
port: 3000
name: "lookout-service"
enabled: true
enabled: true
name: "maester-service"
port: 3002
enabled: true
useSentinels: false
weather we should use sentinels for redis
name: "maester-redis-service"
port: 6379
enabled: false
name: "platform-storage-slugs-service"
port: 9999
enabled: true
name: "platform-storage-slugs-loadbalancer"
port: 9999
enabled: true
name: "quota-service-service"
port: 3002
enabled: true
name: "raven-service"
port: 8070
enabled: false
name: "s3-service"
port: 3000
name: "scheduler-service"
enabled: true
enabled: true
enabled: true
name: "steward-service"
port: 8200
pssBackwardCompatibility: false
enabled: true
name: "webhooks-service"
port: 5000
enabled: true
Prometheus: These parameters enable data scrapping from the services. All data is sent to the Prometheus service. Our team uses for monitoring and alerting purposes.
admiral: "true"
api: "true"
branRead: "true"
branWrite: "true"
facelessApi: "true"
facelessTokenRefresher: "true"
ironBank: "true"
maester: "true"
s3: "true"
cache: "true"
raven: "true"
scheduler: "true"
fluentd: "true"
webhooks: "true"