Static API infrastructure settings are automatically managed.
Hide stackTrace, stackTraceStr and logTail in error replies
Ensures the dku_http_request_metadata variable is populated with real data
Use a cluster id, not name. Variables are allowed with a ${} syntax.
kubectl context to use (empty = use default)
Kubernetes namespace to use (empty = use default)
Path to the config file for Kubectl (empty = use default)
Additional properties about this config, for use by DSS. For specific use cases.
Hostname of the images registry. Your local "docker" command needs to have write access to this registry, and your Kubernetes cluster needs to have read access to this registry. If not set, the built image is not pushed (only for testing purpose using Minikube)
Optional: The secret name is used in the Kubernetes imagePullSecrets manifest section. This is required if your container registry is private and your cluster needs to authenticate to it for pulling images.
Absolute path to a shell script. Receives the repository url, image name & tag as arguments. This script should support being called on an already-existing image/tag.
Prefix all images being pushed by this. When using Google Kubernetes Engine (with gcr.io repository), this needs to start by the project-name/

Advanced settings

Leave empty to use the default
Build an intermediate image with code environments, only rebuilt when a code environment changes
Tweak permissions in the image for compatibility with Openshift. Takes a noticeable amount of time when building image.

Pod settings

These settings control the extensions to the pods of the underlying Kubernetes deployments.
Pod enhancers can provide additional capabilities, notably for advanced autoscaling. Please refer to the documentation for more details.
Name of a service account (optional)
Indicates if service account name can also be defined in deployment settings.

Additional environment variables

Environment variables to define in the deployments.
Indicates if environment variables should be defined using a Kubernetes Secret.
Indicates if environment variables can also be defined in deployment settings.

Additional labels

Labels to add to the deployments.
Indicates if labels can also be defined in deployment settings.

Additional annotations

Annotations to add to the deployments.
Indicates if annotations can also be defined in deployment settings.
These settings control how the APIs are exposed to the outside world. These settings can be overridden on a per-deployment basis.

Replication settings

These settings control the scalability of the underlying Kubernetes deployments.
These settings can be overridden on a per-deployment basis.
Number of pod replicas in Kubernetes
Number of seconds to wait for the Deployment to progress before the system reports back that it has failed progressing ('.spec.progressDeadlineSeconds'). Set to default value of 600 if empty.

API Node Server Sizing and tuning

These settings control internal sizing parameters of the API node server.
These settings can be overridden on a per-deployment basis.
Max Java heap memory for API node server. Leave empty for default
GC algorithm for API node server. Leave empty for default.
Additional command-line options for API node server. Leave empty for default.

Container limits

These settings control CPU and memory limits that are set on each container.
These settings can be overridden on a per-deployment basis.
It is recommended to be familiar with Kubernetes "request" and "limit" parameters to use this.
Memory request for containers in MB. -1 = default (inherit namespace settings)
Memory limit for containers in MB. -1 = default (inherit namespace settings)
CPU request for containers (0.5 = 50% of a core, 2 = 2 cores). -1 = default (inherit namespace settings)
CPU limit for containers (0.5 = 50% of a core, 2 = 2 cores). -1 = default (inherit namespace settings)
Custom Kubernetes limits key-value. For example, on Google Kubernetes Engine, use nvidia.com/gpu = 1 to get a GPU node