Edge - Configuring "REGISTRY_PATH" for a private registry installation

Forum
1

Hello,

I was working on an installation of an C8Y Edge platform with a private registry thanks to this documentation : Configuring Edge to use a private registry - Cumulocity Release 2025 documentation

But we are facing an issue as we need to have a dedicated path on top of the cumulocity path.
Ex :

  • The operator tries to request : REGISTRY_HOST:REGISTRY_PORT/edge/dependencies/dependencies.yaml:2025.0.10

  • We want the operator to request : REGISTRY_HOST:REGISTRY_PORT/REGISTRY_PATH/edge/dependencies/dependencies.yaml:2025.0.10

Is there an hidden parameter to add this?

Best regards,

2

Hello @simon.radier ,

Thank you for reaching out.

Currently, we do not support customising the registry path beyond the default structure. Additionally, the sync script functionality is planned to be deprecated in the upcoming 2026 release.

For scenarios where a custom/private registry structure is required, we recommend using our installer tool along with the offline package. Kindly refer to our quickstart guide (ref: Quickstart - Cumulocity Release 2025 documentation ).

Please let us know if you would like guidance on setting this up, and we’ll be happy to assist.

Best regards,
Team Cumulocity

1 Like
3

But does it mean that the installation on an existing kubernetes will not be supported anymore?

Best regards,

4

Hi Simon,

Please note that installation on existing Kubernetes clusters is still fully supported. The only change is that the registry sync feature is being deprecated.

Best regards,
Team Cumulocity