chart_name: nplus-environment-backend

chart_description: Installs Namespace-Wide Resources such as the conf PVC and the ptemp PVC


key: env

description: Sets additional environment variables for the configuration.


key: envMap

description: Sets the name of a configMap, which holds additional environment variables for the configuration. It is added as envFrom configMap to the container.


key: envSecret

description: Sets the name of a secret, which holds additional environment variables for the configuration. It is added as envFrom secretRef to the container.


key: fullnameOverride

description: This overrides the output of the internal fullname function


This is the version of the component, used for display @internal -- set by devOps pipeline, so do not modify


Sets the language of the main service (in the *service* container). This is used for instance if you turn OpenTelemetry on, to know which Agent to inject into the container.


lists the ports this component exposes. This is important for zero trust mode and others.


The http port this component uses (if any). In zero trust mode, this will be disabled. @internal -- this is a constant value of the component and should not be changed.


The tls / https port, this component uses (if any) @internal -- this is a constant value of the component and should not be changed.


A potential rmi port, this component uses (if any) @internal -- this is a constant value of the component and should not be changed.


A potential tcp port, this component uses (if any) @internal -- this is a constant value of the component and should not be changed.


A potential tls / tcps port, this component uses (if any) @internal -- this is a constant value of the component and should not be changed.


sets provider (partner, reseller) information to be able to invoice per use in a cloud environment


The container name of the main service for this component. This is used to define where to inject the telemetry agents, if any


A optional parameter to indicate the stage (DEV, QA, PROD, ...) this component, instance or environment runs in. This can be used in template functions to add the stage to for instance the service name of telemetry services like open telemetry. (see telemetry example)


sets tenant information to be able to invoice per use in a cloud environment


the type of the component. You should not change this value, except if you use a pipeliner in core mode. In core mode, it should be *core*, else *pipeliner* This type is used to create cluster communication for nappl and nstl and potentially group multiple replicaSets into one service.


Sets the wave in which this component should be deployed within an ArgoCD deployment if unset, it uses the default wave thus all components are installed in one wave, then relying on correct wait settings just like in a helm installation


key: minReplicaCountType

description: if you set minReplicaCountType, a podDesruptionBudget will be created with this value as minAvailable, using the component type as selector. This is useful for components, that are spread across multiple replicaSets, like sharepoint or storage layer


key: nameOverride

description: This overrides the output of the internal name function


key: nodeSelector

description: select specific nodes for this component


this is the name of the common config storage. please see section "Storage" for more information


this is the size of the common config storage. please see section "Storage" for more information


you can set the volumeName to the value of a pre-existing volume to avoid having the PV created for you by the csi driver provisioner


this is the name of the common persistant temp storage. please see section "Storage" for more information


this is the size of the common ptemp storage. please see section "Storage" for more information


key: telemetry

description: Settings for telemetry tools


turns Open Telemetry on


Sets the service name for the telemetry service to more convenient identify the displayed component Example: "{{ .this.meta.type }}-{{ .instance.name }}"


key: terminationGracePeriodSeconds

description: Sets the terminationGracePeriodSeconds for the component If not set, it uses the Kubernetes defaults


key: timezone

description: set the time zone for this component to make sure log output has a specific timestamp, internal dates and times are correct (like the creationDate in nappl) etc.

default: `Europe/Berlin`


key: tolerations

description: Set tolerations for this component


description: Turn debugging *on* will give you stack trace etc.  Please check out the Chart Developer Guide

default: `false`


description: in case you use the argoCD Wave feature, you might think about switching off the waitFor mechanism, that makes sure PODs are only started after pre-requisites are fulfilled. You can disable the starndard wait mechanism, but at your own risk, as this might start components even if they are not intended to run yet.


description: If you use argoCD, you most likely want to use the argo Wave Feature as well, making sure the components of an instance are deployed ordered. However, in DEV you might want to disable this to allow live changing components while previous waves are not finished yet.


description: By default, the namespace is rendered into the manifest. However, if you want to use `helm template` and store manifests for later applying them to multiple namespaces, you might want to turn this `false` to be able to use `kubectl apply -n <namespace> -f template.yaml` later

default: `true`


description: in Maintenance Mode, all *waitFor* actions will be skipped, the *Health Checks* are ignored and the pods will start in idle, not starting the service at all. This will allow you to gain access to the container to perform recovery and maintenance tasks while having the real container up.


description: You can turn Comment rendering *on* to get descriptive information inside the manifests. It will also fail on depricated functions and keys, so it is recommended to only switch it off in PROD