chart_name: nplus-instance

chart_description: nplus Instance, an umbrella chart for orchestrating the components in a nplus Instance


sets the name of the image to use for this component @internal -- set by devOps pipeline, so do not modify


sets the repo from where to load the image. This can be overridden on environment or instance level in case you have your own repo for caching and security reasons


defines the tag for this component @internal -- set by devOps pipeline, so do not modify


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


Defines the ArgoCD wave in which this component should be installed.  This setting only applies to scenarios, where ArgoCD is used as handler


Defines what condition needs to be met before this components starts


sets the dns of the *nscale Server Storage Layer*, that should be configured


sets the dns of the *nscale Rendition Server*, that should be configured


enable a *nscale Administrator Web* component in this instance


deploy any solution using GBA, Standard Apps or shell copy with this generic deployment chart


enable a *nscale CMIS Connector* component in this instance


enable an internal *Postgres Database* in this instance


enable a *nscale ERP CMIS Connector* component in this instance


enable a *nscale ERP Proxy Connector* component in this instance


enable a *nscale ILM Connector* component in this instance


enable a *nscale Monitoring Console* component in this instance


enable a consumer *nscale Application Layer* component in this instance


enable a dedicated jobs *nscale Application Layer* component in this instance please also make sure to set the *jobs* setting


enable a *nscale Server Storage Layer* component in this instance If you are in a **High Availability** scenario, disable this


enable an additional *nscale Server Storage Layer* node in this instance within a **High Availability** scenario.


enable a *nscale Process Automation Modeler* component in this instance


enable *nscale Pipeliner* component in this instance


download, deploy and run any git asset or script prior to installation of the components


enable a *nplus Remote Management Server* component in this instance If you are in a **High Availability** scenario, disable this


enable an additional *nplus Remote Management Server* in this instance within a **High Availability** scenario.


enable a *nscale Rendition Server* component in this instance


enable a *nscale Sharepoint Connector* component in this instance


enable an additional *nscale Sharepoint Connector* component in this instance for another set of configuration parameters


This section is for the single-instance-mode in which all environement components are integrated into the instance


This is for *Single-Instance-Mode* **only**. Read the docu before enabling this. the backend components holds the common storages / PVCs for conf and ptemp umong other common environmental resources


This is for *Single-Instance-Mode* **only**. Read the docu before enabling this. DAV gives you WebDAV access to your conf and ptemp volumes


This is for *Single-Instance-Mode* **only**. Read the docu before enabling this. The Operator will let you query the Custom Resources for nscale, e.g. `kubectl get nscale`


This is for *Single-Instance-Mode* **only**. Read the docu before enabling this. the toolbox has a git client installed and is suitable for pulling, pushing, copying  stuff into the pool, fonts, certificates, snippets and configuration files


enable a *nscale Web* component in this instance


enable a *nscale WebDAV Connector* component in this instance


key: database

description: For the Database, we use a postgres 16 Ceyoniq uses docker.io/bitnami/postgresql:16


sets the name of the image to use for this component @internal -- set by devOps pipeline, so do not modify


sets the repo from where to load the image. This can be overridden on environment or instance level in case you have your own repo for caching and security reasons


defines the tag for this component @internal -- set by devOps pipeline, so do not modify


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


Defines the ArgoCD wave in which this component should be installed.  This setting only applies to scenarios, where ArgoCD is used as handler


Defines what condition needs to be met before this components starts


DB account (if not using a secret)


nscale DB server dialect


nscale DB server driverclass


name of the nscale DB


DB password (if not using a secret)


weather the password is stored encrypted


DB schema name


DB credential secret (account, password)


The URL to the database


Sets the root for this instance, where incoming root traffic should be redirected to


description: sets the global ingressclass for all components to use - if they do not define a specific one, for example if there are separate controllers for internal and external traffic

default: `public``


if you do not define an issuer to generate the tls secret for you, you still can have a self signed certificate generated for you, if you set this to true. The default is true, so either you have an issuer or not, you will always end up with a certificate. Set an empty issuer and createSelfSignedCertificate to false to have no certificate generated and use an external or existing secret. Then make sure the secret matches.


Sets the global domain within the instance to be used, if the component does not define any domain. If this remains empty, no ingress is generated Example: `{{ .instance.group }}.lab.nplus.cloud`


Sets the name of the issuer to create the tls secret. Very common is to have it created by  cert-manager. Please see the documentation how to create a cert-manager cluster issuer for example. If no issuer is set, no certificate request will be generated


description: Specify the namespace in which the ingress controller runs. This sets the firewall rule / networkPolicy to allow traffic from this namespace to our pods. This may be a comma separated list

default: `ingress, kube-system, ingress-nginx`


description: Sets the name of the tls secret to be used for this ingress, that contains the private and public key. This secret is then either generated by cert-manager or self signed by helm - or not created

default: `{{ .this.ingress.domain }}-tls`


optionally sets a whitelist of ip ranges (CIDR format, comma separated) from which ingress is allowed. This is an annotation for nginx, so won't work with other ingress controllers


The group of the instance. This is used for the networkPolicies. Only Pods within one group are allowed to communicate if you enable the nplus Network Policies. By default, this is set the same as the instance name


The name of the instance. Should this name be identical to the namespace name, then  the prefix will be dropped. By default, this is the .Release.Name


Globally set the license secret name


defines the nplus toolbox name to be used for the *wait* feature


defines the nplus toolbox pull policy to be used for the *wait* feature


defines the nplus toolbox image to be used for the *wait* feature


defines the tag for the logforwarder (FluentBit) @internal -- set by devOps pipeline, so do not modify


Sets the nscale version of this deployment / instance. This is used by the operator to display the correct version e.g. in the Web UI. @internal -- this is set by the devOps pipeline, so do not modify


The technical account to login with


The domain of the technical account


sets the *nscale Server Application Layer* host to be used. As this is a global option, it can be overridden at component level.


the instance of *nscale Server Application Layer* to be used @internal -- As this is depricated for nscale 10, you should never modify this.


The password of the technical accunt (if not set by secret)


sets the *nscale Server Application Layer* port to be used. As this is a global option, it can be overridden at component level. if you switch to zero trus mode or change the nappl backend to https, you want to modify this port to 8443


An optional secret that holds the credentials (the keys must be `account` and `password`)


wether to use ssl or not for the advanced connector


sets the instance, from which Administration is allowed


sets the namespace, from which Administration is allowed


creates NetworkPolicies for each  component.


if defined, creates a default NetworkPolicy to handle  egress Traffic from the instance. Possible Values: deny, allow, none


if defined, creates a default NetworkPolicy to handle  ingress Traffic to the instance. Possible Values: deny, allow, none


sets the instance, from which Monitoring is allowed


sets the namespace, from which Monitoring is allowed


sets the instance, from which Process Automation Modeling is allowed


sets the namespace, from which Process Automation Modeling is allowed


enables zero trust on the instance. When enabled, no unencrypted http connection is allowed. This will remove all http ports from pods, services, network policies and ingress rules


if you use a OpenTelemetry as a telemetry collector, you can enable it here. This will add the annotations to some known pods for the injector to use agents inside the pods for telemetry collection.  This often goes along with the `language` setting in the meta section to tell the  telemetry collector which agent to inject.


defines the nplus toolbox name to be used for the *wait* feature


defines the nplus toolbox pull policy to be used for the *wait* feature


defines the nplus toolbox image to be used for the *wait* feature


defines the nplus toolbox tag to be used for the *wait* feature @internal -- set by devOps pipeline, so do not modify


sets the name of the image to use for this component @internal -- set by devOps pipeline, so do not modify


sets the repo from where to load the image. This can be overridden on environment or instance level in case you have your own repo for caching and security reasons


defines the tag for this component @internal -- set by devOps pipeline, so do not modify


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


Defines the ArgoCD wave in which this component should be installed.  This setting only applies to scenarios, where ArgoCD is used as handler


Defines what condition needs to be met before this components starts


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


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


When using multiple nstl Instances with different configurations, you still might want to use a cluster service for HA access This will generate one for you.


key: rms

description: rms is not a Ceyoniq component, but a part of nplus


key: sharepoint

description: For SharePoint Connector, there is no entry in Github yet, so we set it hardcoded TODO: 9.3: Test again later, if there is a valid github entry.


Set the context Path for the cluster Ingress. Make sure also the members are listening to this path


When using multiple SharePoint Connectors with different configurations, you still might want to use a retrieval cluster for HA so you can enable the clusterService and define the context path.


Defines the context path of this sharepoint instance, in case you might have multiple instances. We do not want them to consume the same ingress path, because it would block the ingress from being created.