> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/kubernetes-security/mirror-connector-images-to-a-private-registry.md). # Mirror connector images to a private registry Mirror container images from the Cortex Cloud source registry to your private registry, enabling secure, air-gapped Kubernetes cluster deployments. {% hint style="info" %} **Notice** Licensed under the Apache License, Version 2.0. {% endhint %} ### What is image mirroring? Image mirroring is the process of copying container images from a source registry to a private registry under your control. This capability is essential for organizations operating in air-gapped environments, restricted networks, or those requiring centralized image governance. The Cortex Cloud Konnector Image Mirroring CLI (kcli) automates this process by pulling multi-architecture konnector images from the Cortex source registry, pushing them to your private registry, and rewriting your Helm values file to reference the mirrored images. This eliminates the need for cluster nodes to access external registries during deployment, reducing attack surface and enabling compliance with network isolation policies. ### Why image mirroring matters * **Network isolation**: Clusters pull images from internal registries only, not from external sources * **Compliance**: Meets requirements for air-gapped deployments and restricted egress policies * **Supply chain control**: Centralize image governance and scanning before deployment * **Deployment reliability**: Eliminates external registry dependencies during cluster operations ### Scope and limitations #### What kcli does * Pulls multi-architecture konnector images from the Cortex source registry * Pushes images to your private registry * Rewrites your Helm values file to reference the mirrored images #### What kcli does not do * Execute `helm install` or `helm upgrade` commands (the portal's installation wizard is the source of truth) * Create Kubernetes Secret resources in your cluster * Manage Namespaces, RBAC, or cluster prerequisites * Commit or push the rewritten values file to Git (GitOps workflows must handle this) * Commit or push the rewritten values file to Git (GitOps workflows must handle this) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/kubernetes-security/mirror-connector-images-to-a-private-registry.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.