> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/switch-infrastructure/config-manager/llms.txt.
> For full documentation content, see https://docs.nvidia.com/switch-infrastructure/config-manager/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/switch-infrastructure/config-manager/_mcp/server.

# Config Manager Temporal Deployment Process

Temporal is deployed as part of the Config Manager Helm release. Use the [standard deployment guide](/switch-infrastructure/config-manager/getting-started/getting-started-with-config-manager) for connected environments and the [airgapped deployment guide](/switch-infrastructure/config-manager/deployment/airgapped) for disconnected environments.

## Deployment Inputs

The installer controls Temporal deployment through `nv-config-manager-install.yaml` and generated Helm values:

* `services.temporal`: enables the Temporal API, workers, and related deployment resources.
* `cluster.hostname`: drives public workflow API and Temporal Web hostnames.
* `secrets`: provides database, auth, and integration secrets.
* `rbac`: configures workflow read and execute roles.
* `infrastructure`: configures TLS, gateway, storage, and optional observability.

## Verify Temporal

After deployment, verify the workflow API and Temporal Web routes:

```bash
kubectl get pods -n <namespace> | grep temporal
kubectl get httproutes -n <namespace> | grep -E 'workflow|temporal'
```

Open the workflow API at `https://workflow.<hostname>/docs` and Temporal Web at `https://temporal.<hostname>` if Temporal Web is enabled for the environment.

## Operations

For normal operator actions, use the Config Manager UI. Use Temporal Web for detailed workflow event history, retries, payload inspection, and child workflow troubleshooting. See [Which Interface Should I Use?](/switch-infrastructure/config-manager/getting-started/which-interface-should-i-use).