📚 Sync docs from alaudadevops/tektoncd-operator on 089c9a1a882c7818019615827997cc6a5612e097

edge-katanomi-app2[bot] · edge-katanomi-app2[bot] · commit feeaa010556b · 2025-12-12T08:38:29.000Z
Source: docs: [DEVOPS-43012] remove `docker` in docs (#1002) Author: yzc Ref: refs/heads/release-4.6 Commit: 089c9a1a882c7818019615827997cc6a5612e097 This commit automatically syncs documentation changes from the source-docs repository. 🔗 View source commit: https://github.com/alaudadevops/tektoncd-operator/commit/089c9a1a882c7818019615827997cc6a5612e097 🤖 Synced on 2025-12-12 08:38:29 UTC
diff --git a/.github/SYNC_INFO.md b/.github/SYNC_INFO.md
@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-12-11 09:26:29 UTC
+- **Last synced**: 2025-12-12 08:38:29 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [d2f24f2e5030526a45fc673bd7a75c4bd0aaead6](https://github.com/alaudadevops/tektoncd-operator/commit/d2f24f2e5030526a45fc673bd7a75c4bd0aaead6)
+- **Source commit**: [089c9a1a882c7818019615827997cc6a5612e097](https://github.com/alaudadevops/tektoncd-operator/commit/089c9a1a882c7818019615827997cc6a5612e097)
 - **Triggered by**: edge-katanomi-app2[bot]
-- **Workflow run**: [#118](https://github.com/alaudadevops/tektoncd-operator/actions/runs/20128242238)
+- **Workflow run**: [#120](https://github.com/alaudadevops/tektoncd-operator/actions/runs/20161106324)
 
 ## Files synced:
 - docs/
diff --git a/docs/en/chains/configure/authentication_for_chains.mdx b/docs/en/chains/configure/authentication_for_chains.mdx
@@ -46,15 +46,15 @@ Make sure that any external credentials store, such as the native keychain of th
 Create a secret with config.json:
 
 ```shell
-kubectl create secret generic docker-registry \
+kubectl create secret generic registry-credentials \
     --from-file=.dockerconfigjson=<path/to/.docker/config.json> \
     --type=kubernetes.io/dockerconfigjson \
     -n $NAMESPACE
 ```
 
 #### Create a Secret by providing credentials on the command line
 
-First, you will need access to credentials for your registry (they are in a file called `credentials.json` in this example). Then, create a Docker config type Kubernetes secret:
+First, you will need access to credentials for your registry (they are in a file called `credentials.json` in this example). Then, create a `kubernetes.io/dockerconfigjson` type Kubernetes secret:
 
 ```shell
 kubectl create secret docker-registry registry-credentials \
diff --git a/docs/en/chains/how_to/sbom_verification.mdx b/docs/en/chains/how_to/sbom_verification.mdx
@@ -199,7 +199,7 @@ spec:
     - name: source
       description: The workspace for source code.
     - name: dockerconfig
-      description: The workspace for Docker configuration.
+      description: The workspace for distribution registry configuration.
     - name: signkey
       description: The workspace for private keys and passwords used for image signatures.
 ```
diff --git a/docs/en/chains/how_to/source_code_repository_verification.mdx b/docs/en/chains/how_to/source_code_repository_verification.mdx
@@ -221,7 +221,7 @@ spec:
     - name: source
       description: The workspace for source code.
     - name: dockerconfig
-      description: The workspace for Docker configuration.
+      description: The workspace for distribution registry configuration.
 ```
 
 :::tip
diff --git a/docs/en/chains/how_to/vulnerability_scanning_verification.mdx b/docs/en/chains/how_to/vulnerability_scanning_verification.mdx
@@ -233,7 +233,7 @@ spec:
     - name: source
       description: The workspace for source code.
     - name: dockerconfig
-      description: The workspace for Docker configuration.
+      description: The workspace for distribution registry configuration.
     - name: signkey
       description: The workspace for private keys and passwords used for image signatures.
 ```
diff --git a/docs/en/chains/quick_start/signed_provenance.mdx b/docs/en/chains/quick_start/signed_provenance.mdx
@@ -226,7 +226,7 @@ spec:
     - name: source
       description: The workspace for source code.
     - name: dockerconfig
-      description: The workspace for Docker configuration.
+      description: The workspace for distribution registry configuration.
 ```
 
 :::tip
@@ -251,7 +251,7 @@ In production environments, you should:
   - This format is compliant with Tekton Chains, see [Tekton Chains Type Hinting](../concepts/understanding_tekton_chains.mdx#type-hinting) in above section for more details.
 - `workspaces`: The workspaces for the pipeline.
   - `source`: The workspace for source code.
-  - `dockerconfig`: The workspace for Docker configuration.
+  - `dockerconfig`: The workspace for distribution registry configuration.
 :::
 
 **Need to adjust the configuration**
@@ -303,7 +303,7 @@ spec:
 - `taskRunTemplate`: The task run template.
   - `serviceAccountName`: The service account to use for the pipeline.
 - `workspaces`: The workspaces for the pipeline.
-  - `dockerconfig`: The workspace for Docker configuration.
+  - `dockerconfig`: The workspace for distribution registry configuration.
   - `source`: The workspace for source code.
 :::
 
diff --git a/docs/en/design/pipeline-integration/connector-behavior.mdx b/docs/en/design/pipeline-integration/connector-behavior.mdx
@@ -288,7 +288,7 @@ attributes:
   - params.versions
 
 workspaces:
-- name: docker-config
+- name: registry-creds
   value:
     csi:
       driver: connectors-csi
diff --git a/docs/en/development/run_e2e.mdx b/docs/en/development/run_e2e.mdx
@@ -90,7 +90,7 @@ toolchains:
     testGroup:
       # Default test group
       default: e2e-automation
-    # Base64 encoded Docker configuration file
+    # Base64 encoded distribution registry configuration file
     dockerConfig: <BASE64_ENCODED_DOCKER_CONFIG>
 
   nexus:
@@ -238,7 +238,7 @@ Each toolchain contains the following common configuration items:
 - `token`: Admin user access token
 
 **Harbor**:
-- `dockerConfig`: Base64 encoded Docker configuration file
+- `dockerConfig`: Base64 encoded distribution registry configuration file
 
 **SonarQube**:
 - `token`: Admin user access token
diff --git a/docs/en/development/tektoncd-chains/setup_cosign.mdx b/docs/en/development/tektoncd-chains/setup_cosign.mdx
@@ -126,7 +126,7 @@ kubectl delete pod -n tekton-pipelines -l app=tekton-chains-controller
 
 If you're using OCI storage, you need to set up authentication for the registry:
 
-#### Create a Docker Config Secret
+#### Create a Distribution Registry Config Secret
 
 Create a secret containing your registry credentials:
 
diff --git a/docs/en/hub/tutorials/writing-pipelines.mdx b/docs/en/hub/tutorials/writing-pipelines.mdx
@@ -123,8 +123,8 @@ spec:
   workspaces:
   - name: source-code
     description: Source code workspace
-  - name: docker-config
-    description: Docker registry credentials
+  - name: registry-creds
+    description: Distribution registry credentials
     optional: true
 
   tasks:
@@ -171,7 +171,7 @@ spec:
     - name: source
       workspace: source-code
     - name: dockerconfig
-      workspace: docker-config
+      workspace: registry-creds
 
   finally:
   - name: cleanup
diff --git a/docs/en/pipelines/concepts/pod_templates_concept.mdx b/docs/en/pipelines/concepts/pod_templates_concept.mdx
@@ -251,7 +251,7 @@ Pod template configuration supports the fields listed in the table below.
 | automountServiceAccountToken | **Default:** true. Determines whether Tekton automatically provides the token for the service account used by the Pod inside containers at a predefined path.                                                                                                                                                     |
 | dnsPolicy                    | **Default:** ClusterFirst. Specifies the [DNS policy](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy) for the Pod. Legal values are ClusterFirst, Default, and None. Does **not** support ClusterFirstWithHostNet because Tekton Pods cannot run with host networking. |
 | dnsConfig                    | Specifies [additional DNS configuration for the Pod](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-config), such as name servers and search domains.                                                                                                                         |
-| enableServiceLinks           | **Default:** true. Determines whether services in the Pod's namespace are exposed as environment variables to the Pod, similarly to Docker service links.                                                                                                                                                         |
+| enableServiceLinks           | **Default:** true. Determines whether services in the Pod's namespace are exposed as environment variables to the Pod.                                                                                                                                                         |
 | priorityClassName            | Specifies the [priority class](https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/) for the Pod. Allows you to selectively enable preemption on lower-priority workloads.                                                                                                                  |
 | schedulerName                | Specifies the [scheduler](https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/) to use when dispatching the Pod. You can specify different schedulers for different types of workloads, such as volcano.sh for machine learning workloads.                                          |
 | imagePullSecrets             | Specifies the [secret](https://kubernetes.io/docs/concepts/configuration/secret/) to use when [ pulling a container image](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).                                                                                                |
diff --git a/docs/en/tutorials/helm/deploy_or_upgrade_by_helm_chart_in_registry.mdx b/docs/en/tutorials/helm/deploy_or_upgrade_by_helm_chart_in_registry.mdx
@@ -28,7 +28,7 @@ You'll Build a reusable Pipeline named `helm-oci-deploy` that:
 * An OCI registry with the OCI chart reference and version you intend to deploy, e.g.:
     * `oci://registry.example.com/charts/myapp`
     * Version like `1.2.3` (must exist in the registry)
-* Registry credentials for your OCI registry as a Docker config JSON:
+* Registry credentials for your OCI registry as a `Secret` of `kubernetes.io/dockerconfigjson` type:
     * Create a Kubernetes Secret of type `kubernetes.io/dockerconfigjson` (example below).
 * Cluster access for Helm (choose one):
     * Mount a Kubeconfig Secret,
@@ -38,7 +38,7 @@ You'll Build a reusable Pipeline named `helm-oci-deploy` that:
 
 ### Step 1: Create the Registry Credential Secret
 
-You need a registry credential for your OCI registry as a Docker config JSON.
+You need a registry credential for your OCI registry as a `Secret` of `kubernetes.io/dockerconfigjson` type.
 
 You can refer to the [Prepare Registry Credential](../prepare/prepare_registry_credential.mdx).
 
@@ -97,7 +97,7 @@ spec:
       default: ""
   workspaces:
     - name: registry-creds
-      description: Workspace with docker config at config.json (for OCI auth)
+      description: Workspace with distribution registry config at config.json (for OCI auth)
       optional: true
     - name: kubeconfig
       description: Workspace containing kubeconfig file at ./kubeconfig
diff --git a/docs/en/tutorials/helm/package_and_push_helm_chart.mdx b/docs/en/tutorials/helm/package_and_push_helm_chart.mdx
@@ -28,20 +28,20 @@ You will create a Pipeline with two Tasks:
 * Tekton Pipelines installed on your cluster.
 * A Helm 3.8+ container image (Helm v3 with OCI support).
 * An OCI registry and repository path (e.g., oci://registry.example.com/charts).
-* Push credentials for your OCI registry as a Docker config JSON:
+* Push credentials for your OCI registry as a `Secret` of `kubernetes.io/dockerconfigjson` type:
     * Create a Kubernetes Secret of type `kubernetes.io/dockerconfigjson` (example below).
 * A Git repository that contains a valid Helm chart (directory with `Chart.yaml`, `templates/`, `values.yaml`).
 * Git access to the repository:
     * Public repo: nothing special.
     * Private repo: create a Git credential Secret (SSH or basic-auth).
 
-Why Docker config JSON? Helm uses the same auth config as Docker. We'll point Helm to it via `HELM_REGISTRY_CONFIG`.
+Why `Secret` of `kubernetes.io/dockerconfigjson` type? We'll point Helm to distribution registry via `HELM_REGISTRY_CONFIG`.
 
 ## Step-by-Step Instructions
 
 ### Step 1: Create the Registry Credential Secret
 
-You need a registry credential for your OCI registry as a Docker config JSON.
+You need a registry credential for your OCI registry as a `Secret` of `kubernetes.io/dockerconfigjson` type.
 
 You can refer to the [Prepare Registry Credential](../prepare/prepare_registry_credential.mdx).
 
diff --git a/docs/en/tutorials/java/use-java-image-build-scan-deploy-pipeline.mdx b/docs/en/tutorials/java/use-java-image-build-scan-deploy-pipeline.mdx
@@ -191,7 +191,7 @@ spec:
 - **maven-trust-store**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) containing JKS truststore for private CAs used by Maven.
 - **sonar-settings**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) where SonarQube properties can be mounted.
 - **sonar-credentials**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) containing credentials for use within SonarQube.
-- **dockerconfig**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) for Docker configuration files, such as `config.json` or `.dockerconfigjson`. This is optional and is used for authentication when pushing images to the registry.
+- **dockerconfig**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) for distribution registry configuration files, such as `config.json` or `.dockerconfigjson`. This is optional and is used for authentication when pushing images to the registry.
 - **kubeconfig**: An [Optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) containing kubeconfig file. The name of kubeconfig should be `kubeconfig`. If there is no kubeconfig in this workspace, the workspace will be ignored.
 
 ## Platforms
@@ -397,7 +397,7 @@ spec:
         secretName: sonar-credentials
     - name: dockerconfig
       secret:
-        secretName: docker-credentials
+        secretName: registry-creds
     - name: kubeconfig
       configMap:
         name: kubeconfig
diff --git a/docs/en/tutorials/python/use-python-image-build-scan-deploy-pipeline.mdx b/docs/en/tutorials/python/use-python-image-build-scan-deploy-pipeline.mdx
@@ -191,7 +191,7 @@ spec:
 - **pip-conf**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) consisting of the custom pip settings.
 - **sonar-settings**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) where SonarQube properties can be mounted.
 - **sonar-credentials**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) containing credentials for use within SonarQube.
-- **dockerconfig**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) for Docker configuration files, such as `config.json` or `.dockerconfigjson`. This is optional and is used for authentication when pushing images to the registry.
+- **dockerconfig**: An [optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) for distribution registry configuration files, such as `config.json` or `.dockerconfigjson`. This is optional and is used for authentication when pushing images to the registry.
 - **kubeconfig**: An [Optional workspace](https://github.com/tektoncd/pipeline/blob/v0.65.5/docs/workspaces.md#using-workspaces-in-pipelines) containing kubeconfig file. The name of kubeconfig should be `kubeconfig`. If there is no kubeconfig in this workspace, the workspace will be ignored.
 
 ## Platforms
@@ -392,7 +392,7 @@ spec:
         secretName: sonar-credentials
     - name: dockerconfig
       secret:
-        secretName: docker-credentials
+        secretName: registry-creds
     - name: kubeconfig
       configMap:
         name: kubeconfig
