#Release Notes

#Compatibility and support matrix

The following table shows the compatibility and support matrix between the Alauda DevOps Connectors operator and ACP versions.

Alauda DevOps Connectors Operator Version	ACP Version
v1.2.0	v4.1, v4.0
v1.1.0	v4.1, v4.0
v1.0.8	v4.0
v1.0.4	v4.0

#v1.2.0

#Features and Enhancements

• Support integration with Kubernetes Cluster by using Kubernetes Connector and using Kubernetes Connector in k8s workloads or tektoncd pipelines. more details:
  • Kubernetes Connector Quick Start
  • Understand Kubernetes Connector
  • Using Kubernetes Connector in tektoncd pipelines
• Security updates: Updated base images, dependencies, and resolved security vulnerabilities

#Breaking Changes

No breaking changes.

#Fixed Issues

• Before this update, if the project-ns-prefix feature flag was enabled in ACP, mounting a project-level Connector in a Namespace Pod under an ACP project in the business cluster would result in a permission error. After this update, the issue has been fixed — with the project-ns-prefix feature flag enabled in ACP, a Namespace Pod under an ACP project in the business cluster can now successfully mount a project-level Connector.

#Known Issues

No issues in this release.

#v1.1.0

#Features and Enhancements

• Support using OCI Connector when pulling images in k8s. more details: Using OCI Connector to Deploy Workloads in a Secretless Way
• Security updates: Updated base images, dependencies, and resolved security vulnerabilities

#Breaking Changes

#OCI ConnectorClass resolver-type Change

The OCI connector image address format has been updated to provide better namespace isolation and resource management.

Previous Format: c-connector.connector-ns.svc.cluster.local

New Format: connector.connector-ns.svc.cluster.local/namespaces/<connector-ns>/connectors/<connector-name>

Affected Scenarios:

• Building Images Using OCI Connector in K8S Job: Image address changed from c-harbor.default.svc.cluster.local/test/demo:v1 to harbor.default.svc.cluster.local/namespaces/oci-connector-demo/connectors/oci-connector/test/demo:v1
• Building Images Using OCI Connector in Tekton Pipeline: Image address changed from c-harbor.default.svc.cluster.local/test/demo:v1 to harbor.default.svc.cluster.local/namespaces/oci-connector-demo/connectors/oci-connector/test/demo:v1

Upgrade Instructions: Existing workloads using OCI connectors need to update their image address format to adapt to the new naming convention.

#Services "c-xxx" already exist

After upgrading to v1.1.0, Connectors created in v1.0.8 may encounter the error: services "c-xxx" already exist

This issue occurs because the Service label associated with the Connector proxy has changed, preventing it from matching the old Service.

Resolution: Delete the service resource with the conflicting name, and the Connector status will automatically recover.

#Fixed Issues

• Before this update, when deploying Connectors components on Kubernetes versions before 1.31, a bug in Kubernetes Server-side apply (https://github.com/kubernetes/kubernetes/issues/124605) would continuously update resource `resourceVersion`, potentially causing cluster stability issues. With this update, the connectors-operator now bypasses this issue by preventing reconciliation triggers when only `resourceVersion` changes occur on Kubernetes versions before 1.31.
• Before this update, if the Connectors component was deployed in a namespace other than connectors-system, the `AuthReady` condition of any created OCI Connector would remain in a failed state. With this update, the issue has been resolved. The `AuthReady` condition of an OCI Connector is no longer affected by the namespace in which the Connectors component is deployed and can now accurately reflect the validity of the provided secret.
• Before this update, after deploying the Connectors component, the component status appeared normal. However, when using the connectors-csi driver in a Pod, there were occasional errors indicating:
  "driver name connectors-csi not found in list of registered csi drivers", which caused the Pod to fail to start. With this update, the issue has been resolved. Once the deployment is complete and the component is in a healthy state, Pods can use the connectors-csi driver normally without encountering this intermittent error.

#Known Issues

No issues in this release.

#v1.0.8

#Features and Enhancements

• Security updates: Updated base images, dependencies, and resolved security vulnerabilities

#Fixed Issues

No issues in this release.

#Known Issues

No issues in this release.

#v1.0.4

#Features and Enhancements

#Alauda DevOps Connectors v1.0 (Alpha)

Connectors provide a secure and efficient way to connect to external services and tools and provide an unobtrusive way to integrate with them. Platform teams can easily and securely create connectors while keeping access secrets protected.

Out-of-the-box support:

• git repositories
• oci registries

Connectors also provide extensibility for custom connectors through the API and custom connectors implementation.

#Fixed Issues

No issues in this release.

#Known Issues

No issues in this release.