Deploy configuration reference
Field reference for Deploy config & deploy application. All fields below live in the single Edit Job Deploy panel.
Deployment Trigger
| Value | Meaning |
|---|---|
| Manual | You initiate the deploy manually. |
| Auto | The system deploys automatically when the Pipeline completes successfully. |
ConfigMap / Secret Type
ConfigMap and Secrets share the same two settings. Use ConfigMap for regular configuration, Secrets for sensitive values such as passwords, tokens, or keys.
| Setting | Value | Meaning |
|---|---|---|
| Usage | Environment Variable | Inject data as environment variables into the container. |
| Usage | Data Volume | Mount data as files inside the container. |
| Data format | GUI | Enter data as key/value pairs. Recommended for multi-line data. |
| Data format | YAML | Enter data directly in YAML format (key-value coded input). |
Values YAML — default fields
The Values YAML editor starts pre-filled with this schema:
| Field | Meaning |
|---|---|
ContainerPort | List of container ports to expose. Each entry sets name, port, protocol (e.g. TCP), servicePort, envoyPort, idleTimeout, supportStreaming, useHTTP2. |
EnvVariables | Environment variables for the container, as a list. |
GracePeriod | Seconds the container is given to shut down gracefully. |
LivenessProbe | Kubernetes liveness probe settings: Path, command, failureThreshold, grpc, httpHeaders, initialDelaySeconds, periodSeconds, port, scheme, successThreshold. |
Edit the values to match your application. The schema follows standard Kubernetes deployment configuration.
Deployment Status
| Status | Meaning |
|---|---|
| Running | Deployment is in progress. |
| Success | Deployment completed successfully. |
| Failed | Deployment failed. |
| Cancelled | Deployment was cancelled. |