View Effective Cluster Configuration
A HydrolixCluster spec only needs to define fields that override defaults. When the Hydrolix operator applies the spec, it fills in unset fields with default values, and resolves values inherited from the active scale profile.
The spec stored in the Kubernetes API doesn't show the values the operator actually uses. To see the fully resolved spec, send the sparse spec to the HKW render-spec endpoint.
Use this to:
- Confirm the value the operator will use for a tunable that isn't set in the spec
- Inspect defaults inherited from the active scale profile
- See derived fields like resolved storage classes or reconstructed bucket URLs
Render the resolved spec⚓︎
Get the sparse spec from the cluster and send it to the HKW render-spec endpoint. The endpoint returns the resolved spec with every default and derived value populated.
The required inputs are:
$HDX_NAMESPACE- your Hydrolix cluster namespace$HDX_VERSION- the version of Hydrolix your cluster is running
The output is a complete HydrolixCluster manifest in YAML format. Every tunable, scale setting, and storage configuration field is present with its effective value.
Output options⚓︎
The endpoint accepts additional query parameters that control the output.
| Parameter | Values | Default | Behavior |
|---|---|---|---|
format |
yaml, json |
yaml |
Sets the response format. format=json |
include-pools |
None (flag) | Off | Includes the pools block in the rendered spec. |
Include pools⚓︎
Pool definitions are excluded by default. Pools are typically managed separately from the rest of the cluster spec, so rendering them in the resolved output isn't always useful.
To include pools, add the include-pools query parameter as a bare flag (no value). This shows the effective resource settings each pool inherits from its scale profile.