Artifacts

Ververica Platform: Self-Managed provides simple file storage that enables you to upload files and reference them in Deployments. This article introduces you to artifact management in the Flink fully managed console.

Upload Artifact

1. In the left navigation, click the Namespace selector and select the namespace that you want to open.
2. Click Artifacts.
3. Click Upload artifact.
4. Select the required file.
5. Once uploaded, the artifact will appear in the list on the Artifacts page.

Download Artifact

1. In the left navigation, click the Namespace selector and select the namespace that you want to open.
2. Click Artifacts.
3. Click Download in the Actions column.

Delete Artifact

If an artifact is no longer used, you can delete it by following the steps below.

1. In the left navigation, click the Namespace selector and select the namespace that you want to open.
2. Click Artifacts.
3. Click Delete in the Actions column.

Once deleted, the Artifact will disappear from the list on the Artifacts page.

Configure the Maximum Upload Size

The maximum artifact size accepted by the platform is a Helm value, applied consistently to every service that accepts a job-artifact upload: vvp-gateway, vvp-meta, vvp-appmanager, vvp-premise, and vvp-appagent.

Set it once under global:

1global:
2  upload:
3    maxFileSize: 500MB

The default is 200MB. The value is templated into each service's spring.servlet.multipart.max-file-size. The related max-request-size is not a separate value: it is derived automatically as maxFileSize plus 1MB, which allows for multipart request overhead beyond the file itself.

Verify the rendered result before installing:

1helm template <RELEASE_NAME> \
2  oci://registry.ververica.cloud/platform-charts/ververica-platform \
3  --version 3.1.2 \
4  --values values.yaml | grep -E "max-file-size|max-request-size"