Create a HelmRelease manifest that references the HelmRepository or OCI source and specifies the chart name and version in the chart spec
Add a dependsOn field listing any Kustomization or HelmRelease objects that must be Ready before Flux attempts to install or upgrade this release, such as a cert-manager or ingress-nginx prerequisite
Define a valuesFrom block referencing a ConfigMap or Secret by name, specifying the key within that object that holds the YAML values to merge, and set the optional field appropriately so missing refs don't block reconciliation
Apply the HelmRelease and observe the Flux controller logs to confirm dependency resolution and values merging behavior during the install or upgrade
Verify the rendered Helm values by inspecting the HelmRelease status conditions and the deployed workload configuration
Known gotchas
dependsOn only blocks the HelmRelease from progressing; if the referenced object does not exist at all, Flux enters a waiting state with no error surfaced prominently — always confirm the dependency objects are present and healthy
valuesFrom entries are merged in order; a later entry silently overrides earlier ones for the same key, which can cause environment-specific ConfigMap values to be overridden by a base Secret if the order is wrong
The HelmRelease chart version field accepts semver ranges but the source must actually contain a matching chart version; a mismatch causes a repeated reconciliation failure that looks like a source error rather than a version error
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp