Docs Home
Viewing docs for
BYOCNot available for Self-Managed

BYOC 11.2026

On this page

Overview

Ververica Cloud 11.26 is a security and reliability release for Bring Your Own Cloud. CI pipelines can now register job JAR files that they already wrote to workspace storage. The External URL option for UDF, connector, and catalog JAR files now accepts only files in your workspace storage. The release also fixes Azure workspace creation, workspace access grants, and Single Sign-On login after a profile is deleted. Workspace containers no longer run as root, and updated third-party dependencies address known vulnerabilities.

New Features and Improvements

Register Job JAR Files by Reference

A CI pipeline that writes a job JAR file to your workspace bucket can now register it as an artifact without uploading it again. Register the file with the public API artifacts:saveMetadata endpoint and set check_path to true. A path that does not exist is then rejected when you register it, with a 404 error that names the path, instead of when a deployment starts.

Uploading artifacts through the console and the API works as before.

External URL Limited to Your Workspace Storage

The External URL option in the UDF, connector, and catalog dialogs now accepts only files in your workspace storage, in the namespace you work in. A URL that points to another namespace or to another bucket is refused: the dialog shows a generic error that doesn't name the URL, and the file is not saved.

What this means for you:

  • If a UDF, connector, or catalog uses an External URL outside your workspace storage, copy the JAR file to your workspace storage and update the URL.

Agent Registration Requires a Subscription

Registering a Ververica agent now requires an active AWS Marketplace or Azure Marketplace subscription, for your account or your organization. Without one, registration fails with an error and no agent is created. Previously, the agent was created, but its configuration could not be used, and you had to delete the agent and register it again after subscribing.

Agents that are already registered are not affected.

Non-Root Containers in Workspace Namespaces

The SQL service and web server containers in each workspace namespace now run as non-root users.

Bug Fixes

Azure Workspace Creation After Switching From AWS

On the Create Workspace page, selecting AWS and then switching to Azure left the form unable to submit: clicking Create did nothing and showed no error. You can now create an Azure workspace after switching cloud provider.

Workspace Access After a Namespace Grant

Granting a team or user access to a workspace failed with a conflict error when they already had access to a namespace in that workspace. The grant now succeeds. Removing the last namespace access no longer removes workspace access that you granted separately. Removing workspace access from a team or user that still has namespace access keeps their view access to the workspace, so they can still reach those namespaces.

Single Sign-On Login After a Profile Is Deleted

After a user profile was deleted, a Single Sign-On login with the same identity provider account could still reach the deleted profile for up to 23 hours. Such a login no longer reaches the deleted profile.

Was this helpful?