📚 Sync docs from alaudadevops/connectors-operator on 76053518ae199877855d8f5314758a3be6ed7ef5

Source: feat(docs): enhance documentation for multi-connector usage in Tekton Tasks (#688)
Author: kycheng
Ref: refs/heads/main
Commit: 76053518ae199877855d8f5314758a3be6ed7ef5

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: https://github.com/alaudadevops/connectors-operator/commit/76053518ae199877855d8f5314758a3be6ed7ef5
🤖 Synced on 2026-03-10 03:02:51 UTC

Author: edge-katanomi-app2[bot]

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2026-03-06 06:40:31 UTC
+- **Last synced**: 2026-03-10 03:02:51 UTC
 - **Source repository**: alaudadevops/connectors-operator
-- **Source commit**: [17953aea030c6c6ced679cc31aa22edfdd5ff793](https://github.com/alaudadevops/connectors-operator/commit/17953aea030c6c6ced679cc31aa22edfdd5ff793)
+- **Source commit**: [76053518ae199877855d8f5314758a3be6ed7ef5](https://github.com/alaudadevops/connectors-operator/commit/76053518ae199877855d8f5314758a3be6ed7ef5)
 - **Triggered by**: edge-katanomi-app2[bot]
-- **Workflow run**: [#103](https://github.com/alaudadevops/connectors-operator/actions/runs/22752318896)
+- **Workflow run**: [#104](https://github.com/alaudadevops/connectors-operator/actions/runs/22885086843)
 
 ## Files synced:
 - docs/

docs/en/connectors-harbor/how_to/using_harbor_connector_forward_proxy_in_tekton_pipeline.mdx

@@ -7,6 +7,8 @@ title: Using Harbor Connector Forward Proxy in Tekton Task
 
 Using Harbor Connector Forward Proxy in Tekton Tasks enables centralized management of Harbor credentials and secure access to Harbor registries during Tekton Task execution.
 
+This document also covers how to inject credentials for multiple Harbor registries in a single Tekton Task by mounting multiple Harbor connectors.
+
 ## Requirements for Tekton Task \{#requirements-for-tekton-task}
 
 Not all Tekton Tasks can use Harbor Connector Forward Proxy.
@@ -62,7 +64,7 @@ spec:
         readOnly: true
         driver: connectors-csi
         volumeAttributes:
-          connector.name: "harbor-connector"
+          connectors: "harbor-connector"
           configuration.names: "registry-config"
 ```
 
@@ -86,7 +88,7 @@ spec:
         readOnly: true
         driver: connectors-csi
         volumeAttributes:
-          connector.name: "harbor-connector"
+          connectors: "harbor-connector"
           configuration.names: "registry-config"
   params:
     - name: cmd
@@ -95,11 +97,44 @@ spec:
         buildah push --tls-verify=false myimage harbor.example.com/library/myimage:v1
 ```
 
+### Injecting Credentials for Multiple Harbor Registries in One Task
+
+If one TaskRun needs to access multiple Harbor registries (for example, pull a base image from Harbor A and push the final image to Harbor B), you can mount multiple Harbor connectors in the same workspace.
+
+For example:
+
+```yaml
+apiVersion: tekton.dev/v1
+kind: TaskRun
+metadata:
+  name: buildah-multi-harbor-registry
+spec:
+  taskRef:
+    name: buildah-cli
+  workspaces:
+    - name: registryconfig
+      csi:
+        readOnly: true
+        driver: connectors-csi
+        volumeAttributes:
+          connectors: "harbor-connector-a,harbor-connector-b"
+          configuration.names: "registry-config"
+  params:
+    - name: cmd
+      value: |
+        source /workspace/registryconfig/.env
+        buildah pull --tls-verify=false harbor-a.example.com/team/base:latest
+        buildah push --tls-verify=false local-image:latest harbor-b.example.com/team/app:v1
+```
+
+**Note:** When multiple connectors are used, configuration files are merged by the CSI Driver. For details, see [Multiple Connectors](../../connectors/concepts/connectors_csi.mdx#multiple-connectors).
+
 **Note:** The `--tls-verify=false` flag is required because the forward proxy intercepts and re-signs TLS traffic. Different CLI tools have different ways to configure insecure registries. Please refer to your CLI documentation for details.
 
 ## Further Reading
 
 - [Using Harbor Connector Proxy in K8S Workload](./using_harbor_connector_in_k8s.mdx) - Learn about the general logic of using Harbor Connector proxy
 - [Harbor ConnectorClass Forward Proxy](../concepts/harbor_connectorclass.mdx#forward-proxy) - Learn about forward proxy configurations
 - [Connectors CSI Built-in Configurations](../../connectors/concepts/connectors_csi.mdx#built-in-configurations) - Learn about built-in configuration files
+- [Connectors CSI Multiple Connectors](../../connectors/concepts/connectors_csi.mdx#multiple-connectors) - Learn how to mount multiple connectors in one volume
 - [Using CSI Volumes in Tekton](https://tekton.dev/docs/pipelines/workspaces/#csi) - Tekton CSI workspace documentation

docs/en/connectors-maven/how_to/using-as-maven-registry-mirror.mdx

@@ -95,7 +95,7 @@ spec:
         imagePullPolicy: IfNotPresent
         env:
         - name: MAVEN_OPTS
-          value: -Dmaven.resolver.transport=wagon
+          value: -Dmaven.resolver.transport=wagon # See: https://maven.apache.org/guides/mini/guide-resolver-transport.html#switching-between-transports
         command:
         - "sh"
         - "-c"
@@ -129,7 +129,7 @@ spec:
           readOnly: true
           driver: connectors-csi
           volumeAttributes:
-            connector.name: "maven-mirror-connector"
+            connectors: "maven-mirror-connector"
             configuration.names: "settings"
 EOF
 ```
@@ -157,4 +157,4 @@ Downloaded from connectors-mirror: https://nexus.example.com/repository/maven-pu
 [INFO] Total time:  42.678 s
 [INFO] Finished at: 2025-09-02T23:14:46Z
 [INFO] ------------------------------------------------------------------------
-```
+```

docs/en/connectors-maven/how_to/using-in-tekton-task.mdx

@@ -7,19 +7,33 @@ title: Using Maven Connector in Tekton Task
 
 Using Maven Connector in Tekton Tasks enables centralized management of tool integration information and secure access to Maven registry during Tekton Task execution.
 
+This document shows how to use the multi-connector capability in one TaskRun to:
+
+- pull dependencies from a mirror Maven repository
+- publish build artifacts to a private Maven repository
+
 ## Requirements for Tekton Task
 
 Not all Tekton Tasks can use Maven Connector.
 
-Maven Connector essentially injects temporary Maven credentials through a Connector CSI Driver. It provides a configuration named `settings` that generates a `settings.xml` file with temporary authentication and `ca.cert` file for trust the connector proxy server.
+Maven Connector injects temporary Maven credentials through the Connectors CSI Driver. It provides a configuration named `settings` that generates a `settings.xml` file with temporary authentication and a `ca.cert` file to trust the connector proxy server.
 
 Therefore, Tekton Tasks must meet the following requirements to use Maven Connector:
 
 **Support mounting a `settings.xml` and `ca.cert` file via Workspace**
 
+## Multi-Connector Scenario
+
+To pull dependencies from a mirror and deploy to a private repository in the same TaskRun, prepare two Maven connectors:
+
+- `maven-mirror-connector`: configured with `useAsMirror=true` for dependency resolution
+- `maven-deploy-connector`: configured for deployment target repository
+
+Then mount both connectors in one workspace using `volumeAttributes.connectors`.
+
 ## Usage Instructions
 
-After confirming that your Tekton Task can use Maven Connector, you can add Maven Connector to the TaskRun YAML file:
+After confirming that your Tekton Task can use Maven Connector, add both connectors to the TaskRun YAML.
 
 For example:
 
@@ -29,27 +43,40 @@ kind: TaskRun
 metadata:
   name: maven-connector-demo
 spec:
-  # .  . .
+  params:
+  - name: GOALS
+    value:
+    - "deploy"
+    - "-Dmaven.resolver.transport=wagon" # See: https://maven.apache.org/guides/mini/guide-resolver-transport.html#switching-between-transports
+    - "-DaltDeploymentRepository=nexus::https://<repository-url>/repository/maven-releases" # Optional if deploy repository is configured in pom.xml
+  # other parameters...
   workspaces:
   - name: settings
     csi:
       driver: connectors-csi
       readOnly: true
       volumeAttributes:
-        connector.name: maven-connector
-        connector.namespace: ""
+        connectors: "maven-mirror-connector,maven-deploy-connector"
         configuration.names: "settings"
   - name: cert
     csi:
       driver: connectors-csi
       readOnly: true
       volumeAttributes:
-        connector.name: maven-connector
-        connector.namespace: ""
+        connectors: "maven-mirror-connector,maven-deploy-connector"
         configuration.names: "settings"
 ```
 
-For workspaces parameters, please refer to [Using Connectors CSI Driver to mount settings.xml file](../concepts/maven_connectorclass.mdx#using-connectors-csi-driver-to-mount-settingsxml-file) in Maven Connector Concepts document.
+In this example:
+
+- `maven-mirror-connector` is used for pulling dependencies from the configured mirror.
+- `maven-deploy-connector` is used when `mvn deploy` uploads artifacts to the private repository.
+- `settings.xml` and `ca.cert` are mounted from the same `settings` configuration.
+
+For workspaces parameters, please refer to:
+
+- [Using Connectors CSI Driver to mount settings.xml file](../concepts/maven_connectorclass.mdx#using-connectors-csi-driver-to-mount-settingsxml-file)
+- [Multiple Connectors in Connectors CSI](../../connectors/concepts/connectors_csi.mdx#multiple-connectors)
 
 For more information about Connectors CSI Driver, please refer to [Connectors CSI Configuration](../../connectors/concepts/connectors_csi.mdx).
 

docs/en/connectors-oci/how_to/using_oci_connector_forward_proxy_in_tekton_pipeline.mdx

@@ -7,6 +7,8 @@ title: Using OCI Connector Forward Proxy in Tekton Task
 
 Using OCI Connector Forward Proxy in Tekton Tasks enables centralized management of OCI registry credentials and secure access to OCI registries during Tekton Task execution.
 
+This document also covers how to inject credentials for multiple registries in a single Tekton Task by mounting multiple OCI connectors.
+
 ## Requirements for Tekton Task \{#requirements-for-tekton-task}
 
 Not all Tekton Tasks can use OCI Connector Forward Proxy.
@@ -62,7 +64,7 @@ spec:
         readOnly: true
         driver: connectors-csi
         volumeAttributes:
-          connector.name: "oci-connector"
+          connectors: "oci-connector"
           configuration.names: "registry-config"
 ```
 
@@ -86,7 +88,7 @@ spec:
         readOnly: true
         driver: connectors-csi
         volumeAttributes:
-          connector.name: "oci-connector"
+          connectors: "oci-connector"
           configuration.names: "registry-config"
   params:
     - name: cmd
@@ -95,11 +97,44 @@ spec:
         buildah push --tls-verify=false myimage registry.example.com/library/myimage:v1
 ```
 
+### Injecting Credentials for Multiple Registries in One Task
+
+If one TaskRun needs to access multiple registries (for example, pull base image from registry A and push final image to registry B), you can mount multiple OCI connectors in the same workspace.
+
+For example:
+
+```yaml
+apiVersion: tekton.dev/v1
+kind: TaskRun
+metadata:
+  name: buildah-multi-registry
+spec:
+  taskRef:
+    name: buildah-cli
+  workspaces:
+    - name: registry-config
+      csi:
+        readOnly: true
+        driver: connectors-csi
+        volumeAttributes:
+          connectors: "oci-connector-registry-a,oci-connector-registry-b"
+          configuration.names: "registry-config"
+  params:
+    - name: cmd
+      value: |
+        source /workspace/registry-config/.env
+        buildah pull --tls-verify=false registry-a.example.com/team/base:latest
+        buildah push --tls-verify=false local-image:latest registry-b.example.com/team/app:v1
+```
+
+> **Note:** When multiple connectors are used, configuration files are merged by the CSI Driver. For details, see [Multiple Connectors](../../connectors/concepts/connectors_csi.mdx#multiple-connectors).
+
 > **Note:** The `--tls-verify=false` flag is required because the forward proxy intercepts and re-signs TLS traffic. Different CLI tools have different ways to configure insecure registries. Please refer to your CLI documentation for details.
 
 ## Further Reading
 
 - [Using OCI Connector Proxy in K8S Workload](./using_oci_connector_in_k8s.mdx) - Learn about the general logic of using OCI Connector proxy
 - [OCI ConnectorClass Forward Proxy](../concepts/oci_connectorclass.mdx#forward-proxy) - Learn about forward proxy configurations
 - [Connectors CSI Built-in Configurations](../../connectors/concepts/connectors_csi.mdx#built-in-configurations) - Learn about built-in configuration files
+- [Connectors CSI Multiple Connectors](../../connectors/concepts/connectors_csi.mdx#multiple-connectors) - Learn how to mount multiple connectors in one volume
 - [Using CSI Volumes in Tekton](https://tekton.dev/docs/pipelines/workspaces/#csi) - Tekton CSI workspace documentation