> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/status-and-specification.md).

# Status & Specification

## Status

<div data-with-frame="true"><figure><img src="/files/hfeB30fXGiKdZKS9r4m6" alt=""><figcaption></figcaption></figure></div>

### Metric cards

Each card appears only when the underlying value has been reported.

<table><thead><tr><th width="220">Card</th><th>Values</th></tr></thead><tbody><tr><td><strong>Database</strong></td><td><code>Provisioned</code> or <code>Pending</code> — whether the participant and validator databases have been created.</td></tr><tr><td><strong>Auth Provisioned</strong></td><td><code>Yes</code> or <code>No</code> — whether managed authentication has completed. Only meaningful when <code>managedKeycloak</code> is enabled.</td></tr><tr><td><strong>Observed Generation</strong></td><td>The generation of the <code>Validator</code> resource the operator last reconciled.</td></tr></tbody></table>

{% hint style="info" %}
**Observed Generation is the field to check after editing a validator.** If it lags behind the resource's current generation, your change has not been reconciled yet — or the reconcile is failing, in which case the conditions table below will say why.
{% endhint %}

### Conditions

| Column              | Contents                                         |
| ------------------- | ------------------------------------------------ |
| **Type**            | The condition type. In practice, always `Ready`. |
| **Status**          | `True`, `False`, or `Unknown`.                   |
| **Reason**          | A short machine-readable cause.                  |
| **Message**         | A human-readable explanation.                    |
| **Last transition** | When the status last changed.                    |

The reasons you will see:

<table><thead><tr><th width="230">Reason</th><th>What to do</th></tr></thead><tbody><tr><td><code>AllApplicationsReady</code></td><td>Nothing — the validator is healthy.</td></tr><tr><td><code>ApplicationNotReady</code></td><td>Go to <a href="/pages/jhTEnSFdrHJF9o1DUx3s">Summary</a> and find which component is <code>Pending</code>.</td></tr><tr><td><code>InvalidSpec</code></td><td>A configuration error. The message names the exact field. Fix the <code>Validator</code> resource and re-apply.</td></tr><tr><td><code>ReconcileError</code></td><td>Something outside the configuration failed — often the database or identity provider being unreachable. Check the operator logs.</td></tr></tbody></table>

Empty state: **No conditions reported** — *The controller has not posted any conditions for this validator.*

***

## Specification

<div data-with-frame="true"><figure><img src="/files/mhKDK4b87dUkoblYnrL3" alt=""><figcaption></figcaption></figure></div>

The validator's configuration, as it exists in the cluster, grouped by section: **Network**, **Participant**, **Validator**, **UI**, **Overrides**, then anything else alphabetically. Each group header shows how many fields it contains, and all groups are expanded by default.

* Booleans display as `Yes` / `No`.
* Long identifiers are truncated with a **Copy** button that copies the full value.
* Empty values show as `-`.

### What is deliberately hidden

{% hint style="warning" %}
This tab is **not** a faithful dump of the resource. Several things are filtered out by design:

* Any field whose path contains `secret`, `password`, `token`, `credential`, `privateKey`, `clientSecret`, or `apiKey`, plus the onboarding secret name — these are never displayed.
* Fields that are set to their default of `enabled: true`. Only `enabled: false` is shown, so an absent `enabled` row means the component is enabled.

For the complete resource, use `kubectl get validator <name> -o yaml`.
{% endhint %}

This is also the fastest way to confirm that a field you set actually took effect. Unknown fields are silently pruned by the Kubernetes API server, so a misspelled field name disappears without an error — if a setting seems to be ignored, look for it here first.

Empty state: **No spec fields** — *No specification fields available.*


---

# 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.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/status-and-specification.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.