📚 Sync docs from alaudadevops/connectors-operator on ed61bf24fa37369c05f9c2c1105de73f13d291ec

edge-katanomi-app2[bot] · edge-katanomi-app2[bot] · commit 5e3601bc8444 · 2025-12-12T13:54:23.000Z
Source: remove docker char in docs (#441) Author: edge-katanomi-app2[bot] Ref: refs/heads/main Commit: ed61bf24fa37369c05f9c2c1105de73f13d291ec This commit automatically syncs documentation changes from the source-docs repository. 🔗 View source commit: https://github.com/alaudadevops/connectors-operator/commit/ed61bf24fa37369c05f9c2c1105de73f13d291ec 🤖 Synced on 2025-12-12 13:54:23 UTC
diff --git a/.github/SYNC_INFO.md b/.github/SYNC_INFO.md
@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-12-12 09:48:31 UTC
+- **Last synced**: 2025-12-12 13:54:23 UTC
 - **Source repository**: alaudadevops/connectors-operator
-- **Source commit**: [6a7385533b855bbdd1a4d7b8e938382f3f48f71a](https://github.com/alaudadevops/connectors-operator/commit/6a7385533b855bbdd1a4d7b8e938382f3f48f71a)
-- **Triggered by**: chengjingtao
-- **Workflow run**: [#64](https://github.com/alaudadevops/connectors-operator/actions/runs/20162848513)
+- **Source commit**: [ed61bf24fa37369c05f9c2c1105de73f13d291ec](https://github.com/alaudadevops/connectors-operator/commit/ed61bf24fa37369c05f9c2c1105de73f13d291ec)
+- **Triggered by**: edge-katanomi-app2[bot]
+- **Workflow run**: [#66](https://github.com/alaudadevops/connectors-operator/actions/runs/20168921193)
 
 ## Files synced:
 - docs/
diff --git a/docs/en/connectors-harbor/concepts/harbor_connectorclass.mdx b/docs/en/connectors-harbor/concepts/harbor_connectorclass.mdx
@@ -158,7 +158,7 @@ Additionally, you need to mount the configuration files into the Pod and configu
 
 The OCI Connector created based on the OCI Connector type provides the following configurations:
 
-**config**: Configuration information required by Docker CLI.
+**config**: Configuration information required by OCI CLI like buildkit, buildah, etc.
 
 - Provides the `config.json` configuration file.
 - Contains the authentication information required to access the proxy.
diff --git a/docs/en/connectors-harbor/how_to/using_harbor_connector_in_k8s_job.mdx b/docs/en/connectors-harbor/how_to/using_harbor_connector_in_k8s_job.mdx
@@ -198,7 +198,7 @@ spec:
     configMap:
       name: dockerfile
 
-  # Mounting docker's config.json to the Pod
+  # Mounting config.json to the Pod
   - name: docker-config
     csi:
       readOnly: true
diff --git a/docs/en/connectors-harbor/how_to/using_harbor_connector_in_workload.mdx b/docs/en/connectors-harbor/how_to/using_harbor_connector_in_workload.mdx
@@ -114,7 +114,7 @@ For more information on Connector resource permissions, see [Connector Scope Per
 
 ### Step 3: Create an Image Pull Secret
 
-Create a Docker registry secret using the ServiceAccount token:
+Create a registry secret using the ServiceAccount token:
 
 ```bash
 kubectl create secret docker-registry harbor-connector-secret \
@@ -136,7 +136,7 @@ http://192.168.x.x:31567/namespaces/harbor-connector-demo/connectors/harbor
 
 - The `docker-username` is set to "u" (a placeholder username)
 - The `docker-password` uses the Service Account token from the previous step
-- The `docker-email` can be any valid email address (used for Docker registry compatibility)
+- The `docker-email` can be any valid email address (used for CNCF Distribution Registry compatibility)
 
 ### Step 4: Patch ServiceAccount with Image Pull Secret
 
diff --git a/docs/en/connectors-harbor/quick_start.mdx b/docs/en/connectors-harbor/quick_start.mdx
@@ -168,7 +168,7 @@ Key parameters in the volume definition:
   - `"buildkitd"`: Generates BuildKit daemon config for insecure registry access
   - if not specified, will be mounted [default configurations](../connectors/concepts/connectors_csi.mdx#built-in-configurations)
 - `mountPath`: Specifies where the configuration file should be mounted in the container:
-  - "/root/.docker" for Docker authentication configuration
+  - "/root/.docker" for buildkit authentication configuration
 
 ### Step 4: Verify Operation
 
diff --git a/docs/en/connectors-oci/concepts/oci_connectorclass.mdx b/docs/en/connectors-oci/concepts/oci_connectorclass.mdx
@@ -204,7 +204,7 @@ and mount the credential configuration files into the Pod and configure the prox
 
 The OCI Connector created based on the OCI Connector type provides the following configurations:
 
-**docker-config**: Configuration credentials required by Container Registry Client.
+**docker-config**: Configuration credentials required by OCI CLI like buildkit, buildah.
 
 - Provides the `config.json` configuration file.
 - Contains the authentication information required to access the proxy.
diff --git a/docs/en/connectors-oci/how_to/using_oci_connector_in_workload.mdx b/docs/en/connectors-oci/how_to/using_oci_connector_in_workload.mdx
@@ -114,7 +114,7 @@ For more information on Connector resource permissions, see [Connector Scope Per
 
 ### Step 3: Create an Image Pull Secret
 
-Create a Docker registry secret using the ServiceAccount token:
+Create a registry secret using the ServiceAccount token:
 
 ```bash
 kubectl create secret docker-registry oci-connector-secret \
@@ -136,7 +136,7 @@ http://192.168.x.x:31567/namespaces/oci-connector-demo/connectors/harbor
 
 - The `docker-username` is set to "u" (a placeholder username)
 - The `docker-password` uses the Service Account token from the previous step
-- The `docker-email` can be any valid email address (used for Docker registry compatibility)
+- The `docker-email` can be any valid email address (used for CNCF Distribution Registry compatibility)
 
 ### Step 4: Patch ServiceAccount with Image Pull Secret
 
diff --git a/docs/en/connectors-oci/intro.mdx b/docs/en/connectors-oci/intro.mdx
@@ -16,7 +16,7 @@ ConnectorsOCI is a specialized connector component that facilitates secure and c
 ConnectorsOCI provides several key capabilities:
 
 - Secure access to container registries (Docker Hub, Harbor, GitHub Container Registry, etc.)
-- Configuration generation for various container tools (Docker, BuildKit, etc.)
+- Configuration generation for various container tools (BuildKit, etc.)
 - Automatic credential injection for registry operations via CSI volumes
 - Proxy mechanism for registry authentication and access
 
diff --git a/docs/en/connectors-oci/quick_start.mdx b/docs/en/connectors-oci/quick_start.mdx
@@ -28,7 +28,7 @@ This approach is particularly useful for:
 ## Notes
 
 - The OCI connector uses CSI driver integration to inject registry credentials securely.
-- Different container tools (Docker, Buildah, etc.) may require specific configuration for insecure registry access.
+- Different container tools (Buildah, etc.) may require specific configuration for insecure registry access.
 - Configuration files generated by the connector expire after 30 minutes.
 
 ## Prerequisites
@@ -188,7 +188,7 @@ Key parameters in the volume definition:
   - `"docker-config"`: Generates authentication config (config.json) needed for any registry operations
   - `"buildkitd"`: Generates BuildKit daemon config for insecure registry access
 - `mountPath`: Specifies where the configuration file should be mounted in the container:
-  - "/root/.docker" for Docker authentication configuration
+  - "/root/.docker" for OCI CLI like buildkit, buildah authentication configuration
   - "/etc/buildkit" for BuildKit configuration
 
 ### Step 4: Verify Operation
diff --git a/docs/en/connectors-oci/trouble_shooting/csi_driver_issues.mdx b/docs/en/connectors-oci/trouble_shooting/csi_driver_issues.mdx
@@ -17,7 +17,6 @@ This guide provides detailed steps for diagnosing and resolving common issues wi
 | Volume mount failures | Incorrect CSI configuration, driver unavailable | Workload can't start |
 | Docker config not found | Wrong mount path, missing volumes | Image pull/push operations fail |
 | Authentication failures | Token issues, configuration errors | Registry access denied |
-| Insecure registry issues | Misconfigured Docker daemon | TLS/certificate errors |
 
 ## Checking CSI Volume Configuration
 
@@ -38,7 +37,7 @@ volumes:
 
 | Configuration Name | Description | Use Case |
 |-------------------|-------------|----------|
-| `docker-config` | Standard Docker client configuration | General container operations |
+| `docker-config` | Standard OCI client like buildkit, buildah authentication configuration | General container operations |
 | `buildkitd` | BuildKit daemon configuration | For BuildKit based operations |
 
 **Common configuration issues**:
@@ -47,7 +46,7 @@ volumes:
 |-------|---------|------------|
 | Incorrect driver name | `MountVolume.SetUp failed` error | Set `driver` exactly to `connectors-csi` |
 | Connector not found | `could not get connector` error | Ensure connector exists in the same namespace |
-| Wrong configuration name | No Docker config generated | Set correct `configuration.names` value |
+| Wrong configuration name | No config generated | Set correct `configuration.names` value |
 | Namespace mismatch | Volume attachment fails | Make sure connector is in the same namespace as pod |
 
 **How to verify**:
@@ -76,7 +75,7 @@ volumeMounts:
 
 | Configuration | Recommended Mount Path | Description |
 |---------------|------------------------|-------------|
-| `docker-config` | `/root/.docker` or `$HOME/.docker` | Docker client configuration directory |
+| `docker-config` | `/root/.docker` or `$HOME/.docker` | OCI client like buildkit, buildah authentication configuration directory |
 | `buildkitd` | `/etc/buildkit` | BuildKit daemon configuration directory |
 
 
@@ -123,7 +122,7 @@ If configuration files are not found, check:
 4. Connector is Ready
 5. Mount path matches container user's expected path
 
-## Examining Docker Configuration Content
+## Examining OCI Client Configuration Content
 
 ### docker-config
 
@@ -161,29 +160,6 @@ insecure-entitlements = [ "network.host", "security.insecure" ]
   http = true
 ```
 
-
-### Insecure Registry Issues
-
-**Symptoms**:
-- `server certificate verification failed` errors
-- TLS handshake failures
-
-**Troubleshooting**:
-1. Verify insecure registry settings are correctly configured:
-   ```bash
-   kubectl exec <pod-name> -n <namespace> -- cat /etc/docker/daemon.json
-   ```
-
-2. Check if the container runtime is using the mounted configuration:
-   ```bash
-   kubectl exec <pod-name> -n <namespace> -- docker info | grep -A 5 "Insecure Registries"
-   ```
-
-3. For containerd, verify proxy address is properly configured:
-   ```bash
-   kubectl exec -it <node-name> -n <namespace> -- cat /etc/containerd/config.toml | grep -A 10 registry
-   ```
-
 ## Advanced Troubleshooting
 
 ### CSI Driver Logs
diff --git a/docs/en/connectors/architecture/index.mdx b/docs/en/connectors/architecture/index.mdx
@@ -49,7 +49,7 @@ The built-in implementation provides comprehensive HTTP/HTTPS protocol support w
 
 For tools requiring specialized authentication mechanisms, custom proxy implementations can be developed. 
 
-**Example**: The OCI ConnectorClass utilizes a custom OCI Plugin Proxy supporting OCI protocol with Bearer Token authorization for registries like Harbor and Docker Registry.
+**Example**: The OCI ConnectorClass utilizes a custom OCI Plugin Proxy supporting OCI protocol with Bearer Token authorization for registries like Harbor and CNCF Distribution Registry.
 
 More information: [Connectors Proxy](../concepts/connectors_proxy.mdx)
 
diff --git a/docs/en/connectors/concepts/connectors_proxy.mdx b/docs/en/connectors/concepts/connectors_proxy.mdx
@@ -45,7 +45,7 @@ Clients access tools by connecting directly to the Connector Proxy Address inste
 
 For tools requiring specialized authentication mechanisms, custom proxy implementations can be developed. These proxies can be implemented as either forward or reverse proxies based on specific requirements.
 
-**Example**: The OCI Connector uses a custom OCI Plugin Proxy that supports OCI protocol with Bearer Token authorization for registries like Harbor and Docker Registry.
+**Example**: The OCI Connector uses a custom OCI Plugin Proxy that supports OCI protocol with Bearer Token authorization for registries like Harbor and CNCF Distribution Registry..
 
 User can develop a custom proxy server and specified in the connectorclass.
 
diff --git a/docs/en/install.mdx b/docs/en/install.mdx
@@ -16,7 +16,7 @@ The Connectors system has a modular architecture with the following components:
 - **ConnectorsCore**: Required core component that provides the foundation for all connector types
 - **ConnectorsGit**: Optional component that adds support for Git services (GitHub, GitLab, etc.)
 - **ConnectorsGitLab**: Optional component that adds support for GitLab-specific features (GitLab CLI, enhanced authentication)
-- **ConnectorsOCI**: Optional component that adds support for container registries (Harbor, Docker Registry, etc.)
+- **ConnectorsOCI**: Optional component that adds support for container registries (Harbor, Distribution, etc.)
 - **ConnectorsK8S**: Optional component that adds support for Kubernetes clusters
 - **ConnectorsMaven**: Optional component that adds support for Maven registries (e.g., Maven Central, or Maven repositories hosted on Sonatype Nexus).
 - **ConnectorsPyPI**: Optional component that adds support for Python package registries (e.g., PyPI, or Python repositories hosted on Sonatype Nexus).
@@ -263,7 +263,7 @@ To add support for GitLab-specific features (GitLab CLI, enhanced authentication
 
 ### Install ConnectorsOCI (Optional)
 
-To add support for container registries, like Harbor, Docker Registry, etc., install the ConnectorsOCI component:
+To add support for container registries, like Harbor, Distribution, etc., install the ConnectorsOCI component:
 
 1. Create the ConnectorsOCI custom resource:
 
