> 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/onboard-the-kubernetes-connector/deploy-the-kubernetes-connector-via-gitops.md).

# Deploy the Kubernetes Connector via GitOps

Deploy and manage the Kubernetes Connector (konnector-bundle Helm chart) across multiple Kubernetes clusters using a complete GitOps setup. Implement this repository structure to use either ArgoCD or Flux CD as your primary controller.

**GitOps controller comparison**

* ArgoCD: Recommended if you want a visual UI for managing deployments, need real-time drift detection, require built-in rollback with history, and prefer a GUI-based workflow.
* Flux CD: Recommended if you want native Helm release management (`helm install`), need Helm hooks support, and prefer a pure CLI/GitOps workflow.

**Prerequisites**

Before you begin, ensure you have the following:

* A Kubernetes cluster with `kubectl` configured.
* The `helm` CLI installed for pulling charts from OCI registries
* The `flux` CLI and/or `argocd` CLI installed.
* A Git repository accessible from within the cluster.
* Access to the `konnector-bundle` OCI registry.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/kubernetes-security/onboard-the-kubernetes-connector/deploy-the-kubernetes-connector-via-gitops.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.