Defaults

Applies toBYOCSelf-Managed v3

1 min read

On this page

Purpose
Procedure
Global Defaults Through Helm Values
Pod Security Context

This section explains how to use deployment defaults to develop a job in fully managed Flink, which can make job development more efficient.

Purpose

To help users avoid complex parameter configuration in the development process, all parameters are used by default for all deployments.

Procedure

In the left navigation, click the Namespace selector and select the namespace that you want to open.
Click Configurations and choose the Deployment Defaults tab.
Fill in the starting parameters. All parameters are listed below.
Click Save Changes.

Starting Parameters

Parameter	Description
Parameter	Description
Checkpointing Interval	The interval at which checkpoints are scheduled. If you do not configure this parameter, the checkpointing feature is disabled.
Min Interval Between Checkpoints	The minimum interval between two checkpoints. If the maximum parallelism of checkpoints is 1, this parameter specifies the minimum interval between two checkpoints.
State Expiration Time	The period of automatic data cleaning for the state, if not filled in, the default value of the deployment engine version will be used.
Flink Restart Strategy	If a task fails and the checkpointing feature is disabled, the JobManager cannot be restarted. If the checkpointing feature is enabled, the JobManager is restarted. Valid values: Failure Rate: The JobManager is restarted if the number of failures within the specified interval exceeds the upper limit. If you select Failure Rate from the Flink Restart Policy drop-down list, you must set the Failure Rate Interval, Max Failures per Interval, and Delay Between Restart Attempts parameters. Fixed Delay: The JobManager is restarted at a fixed interval. If you select Fixed Delay from the Flink Restart Policy drop-down list, you must set the Number of Restart Attempts and Delay Between Restart Attempts parameters. No Restarts: The JobManager is not restarted. This is the default value.
Deployment name	Enter the name of the Python job.

Additional Configuration

Parameter	Description
Parameter	Description
Additional Flink parameters	such as taskmanager.numberOfTaskSlots: 1

Logging

Parameter	Description
Parameter	Description
Allow Log Archives	By default, Allow Log Archives is turned on. After Allow Log Archives is turned on in the Logging section, you can view the logs of a historical job instance on the Logs tab. For more information, see View the logs of a historical job instance.
Log Archives Expires(Unit: day)	By default, the archived log files are valid for seven days.
Root Log Level	You can specify the following log levels. The levels are listed in ascending order of urgency. TRACE: records finer-grained information than DEBUG logs. DEBUG: records the status of the system. INFO: records important system information. WARN: records the information about potential issues. ERROR: records the information about errors and exceptions that occur.
Log Levels	Enter the log name and log level.
Logging Profile	The log template. You can use the system template or configure a custom template.

Global Defaults Through Helm Values

In addition to the namespace-level Deployment Defaults described above, Ververica Platform 3.1.2 exposes several install-time default blocks as Helm values, so operators can set platform-wide defaults declaratively in values.yaml.

Helm value	What it configures
Helm value	What it configures
globalDeploymentDefaults	Default resource allocation (CPU and memory) for JobManager and TaskManager pods, applied to every deployment.
flinkConfigurationStream	Default Flink configuration applied to stream deployments.
flinkConfigurationBatch	Default Flink configuration applied to batch deployments.

Note

An override replaces the entire block. Include any field the platform sets by default if you want to keep it alongside your override.

YAML

1vvp-appmanager:
2  globalDeploymentDefaults: |-
3    spec:
4      template:
5        spec:
6          resources:
7            jobmanager:
8              cpu: 1
9              memory: 2Gi
10            taskmanager:
11              cpu: 1
12              memory: 2Gi
13  flinkConfigurationStream: |-
14    spec:
15      template:
16        spec:
17          flinkConfiguration:
18            execution.checkpointing.interval: 10s
19  flinkConfigurationBatch: |-
20    spec:
21      template:
22        spec:
23          flinkConfiguration:
24            execution.runtime-mode: BATCH

Known limitations

Warning

Kubernetes pod fields, such as volume mounts, and generic flinkConfiguration set directly under globalDeploymentDefaults don't currently reach JobManager and TaskManager pods. For certificate mounts or other pod-level customization, use the namespace-level Deployment Defaults described above, which support these fields today. Global defaults for session clusters aren't available through Helm values yet.

Pod Security Context

Ververica Platform 3.1.2 sets a default file system group on JobManager and TaskManager pods, so a mounted volume such as a PVC or ConfigMap at /mnt is writable by the non-root Flink user with no configuration on your part:

YAML

1securityContext:
2  fsGroup: 10999
3  fsGroupChangePolicy: OnRootMismatch

This applies automatically to both deployments and session clusters. You no longer need to set spec.securityContext.runAsGroup: 0 manually for the general case.

When you still need runAsGroup: 0

Some storage backends, for example NFS-based or other RWX volumes, don't get re-owned by the default file system group and still require an explicit runAsGroup: 0. Set this through the namespace-level Deployment Defaults API or UI described above, not through the Helm globalDeploymentDefaults value: Kubernetes pod fields set there don't yet reach JobManager and TaskManager pods (see the known limitation earlier on this page).

Was this helpful?

Yes No