> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/kubernetes/weka-operator-deployments/cloud-deployment-manager-kubernetes-deployment-types/deploy-axon-on-kubernetes-using-the-cdm.md).

# Deploy Axon on Kubernetes using the CDM

Use Cloud Deployment Manager to generate a converged Axon deployment for Kubernetes.

Generate WEKA Operator deployment artifacts for an Axon (converged) deployment with the Cloud Deployment Manager (CDM) wizard. Axon co-locates WEKA backends with your workload or GPU nodes and adds a client configuration. Use this deployment type for GPU or compute clusters where storage and workloads share the same nodes.

Access the wizard at Cloud Deployment Manager and sign in with your WEKA account. Select **Kubernetes** as the target platform, then select **Axon (converged)**.

### Before you begin

Complete the same preparation as the Dedicated flow. See **Before you begin** in [Deploy dedicated WEKA on Kubernetes using the CDM](/kubernetes/weka-operator-deployments/cloud-deployment-manager-kubernetes-deployment-types/deploy-dedicated-weka-on-kubernetes-using-the-cdm.md).

### Procedure

The Axon flow contains 8 steps and reuses the Dedicated flow building blocks.

1. Complete the following steps as described in [Deploy dedicated WEKA on Kubernetes using the CDM](/kubernetes/weka-operator-deployments/cloud-deployment-manager-kubernetes-deployment-types/deploy-dedicated-weka-on-kubernetes-using-the-cdm.md): **Set up the operator**, **Define the cluster**, **Size the capacity**, **Configure drive signing**, and **Configure networking**. The Protocols step doesn't apply to Axon.
2. Continue with **Configure the client**, described below.
3. Complete **Choose driver distribution** and **Set debuggability** as described in the same topic. The CSI driver and Stateless clients steps don't apply to Axon.
4. **Configure the client:** The **Client** step (step 6 of 8) generates a WekaClient resource for the co-located workload or GPU nodes. The client runs on the same nodes as the cluster and uses the cluster network by default.
   1. Set **Client Cores**: the number of cores allocated to the WEKA client on each node (default: 4).
   2. Keep **Advanced Client Network** disabled unless the client needs a different network than the cluster. When enabled, set **Client Data NICs** or **Client Device Subnets (CIDR)** for the client data path.

<details>

<summary>Client screen</summary>

<div data-with-frame="true"><figure><img src="https://2745724548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZW262oqYA8pNNfGvXjHa%2Fuploads%2Fo4tzXS04nIRSBZvmAzPD%2Fcdm_k8s_axon_6_clients.png?alt=media&amp;token=fd7d805a-3b1b-46a5-bab4-27f496345c1e" alt=""><figcaption></figcaption></figure></div>

</details>

5. Select **Next**.

The **Output** manifest includes the generated WekaClient resource, named `<cluster>-client`, with the new cluster as its target. Apply it together with the rest of the output.

### Apply the generated configuration

Apply the generated output the same way as the Dedicated flow. See Apply the generated configuration in Deploy WEKA on Kubernetes using the Cloud Deployment Manager. The output also includes the WekaClient resource generated in the Client step.

To save or reload this configuration, see **Save and reload a configuration** in [Deploy dedicated WEKA on Kubernetes using the CDM](/kubernetes/weka-operator-deployments/cloud-deployment-manager-kubernetes-deployment-types/deploy-dedicated-weka-on-kubernetes-using-the-cdm.md).

**Related topics**

* [Cloud Deployment Manager Kubernetes deployment types](/kubernetes/weka-operator-deployments/cloud-deployment-manager-kubernetes-deployment-types.md)
* [Deploy dedicated WEKA on Kubernetes using the CDM](/kubernetes/weka-operator-deployments/cloud-deployment-manager-kubernetes-deployment-types/deploy-dedicated-weka-on-kubernetes-using-the-cdm.md)
* [WEKA Operator full deployment workflow](/kubernetes/weka-operator-deployments/weka-operator-full-deployment-workflow.md)


---

# 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://docs.weka.io/kubernetes/weka-operator-deployments/cloud-deployment-manager-kubernetes-deployment-types/deploy-axon-on-kubernetes-using-the-cdm.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.