Release Notes
Tip
The maintenance period for version v4.3.x is from 15 Sep, 2025 to 15 Jan, 2026.
TOC
Compatibility and support matrix
The following table shows the compatibility and support matrix between the Alauda DevOps Pipelines operator and ACP versions.
v4.3.0
New and Optimized Features
Pipeline
- With this update, Helm application management capabilities are integrated, including:
- Package or Push a Helm Chart to an OCI Registry.
- Deploy or Upgrade from an OCI-hosted Helm Chart.
- Deploy or Upgrade from Helm Charts in Git Repo.
- With this update, when creating a
PipelineRunon the UI, preview ofPipelineresources is supported.
Trigger
- With this update,
TriggerTemplatesupports selectingPipelinefromHubas the triggering resource. - With this update,
TriggerTemplatethat specifiesPipelineRunas the resource supports direct execution.
Hub
- With this update, it is supported to customize the
Catalogin theHuband allow registration of customPipelineorTaskin theHub.
Breaking Changes
No breaking changes in this release.
Fixed Issues
- Before this update, when users configured the tekton-hub-api-ssh-crds Secret for Tekton Hub to clone private repositories using SSH keys, the configuration was not properly applied and code repositories could not be cloned successfully even after restarting the pods. With this update, the tekton-hub-api-ssh-crds Secret configuration is correctly processed and applied, allowing Tekton Hub to successfully clone code from private repositories using SSH authentication.
- Before this update, when executing Tekton Pipeline workflows, users occasionally encountered random test case failures due to Out Of Memory (OOM) errors in init containers, which terminated with exit code 137 and caused pipeline execution failures. With this update, init container memory allocation has been optimized to prevent OOM errors, ensuring stable and reliable pipeline execution during frequent e2e testing scenarios.
Known Issues
- If Pipelines with resolver Tasks encounter webhook validation timeouts during Task retrieval, the pipeline may fail intermittently without automatic retry. To resolve this issue, manually restart the failed pipeline run as the system does not currently implement retry logic for retryable webhook validation errors.