# GetUpgradeStatus

**POST /redpanda.core.admin.v2.FeaturesService/GetUpgradeStatus**

Reports observability for the upgrade-finalization lifecycle: the
 cluster's active logical version, the logical version each member
 reports (i.e. what its binary supports), whether the cluster is
 eligible to finalize, and the active version that a
 FinalizeUpgrade would produce. Read-only; intended to be polled
 before and after FinalizeUpgrade.

 The response reflects the controller leader's view; the request is
 transparently redirected there.


## Servers
- http://localhost:9644: http://localhost:9644 ()



## Parameters
### Headers

- **Connect-Protocol-Version** (number)
  Define the version of the Connect protocol

- **Connect-Timeout-Ms** (number)
  Define the timeout, in ms




### Body: application/json (object)

object

## Responses
### 200
Success

#### Body: application/json (object)
- **activeVersion** (integer | string)
  The cluster's current active logical version. This is also the
   downgrade floor: the cluster can still roll back to a binary that
   supports this version. When state is FINALIZATION_STATE_FINALIZED
   this equals version_after_finalization (no downgrade possible).

- **autoFinalizationEnabled** (boolean)
  Whether the cluster advances the active version automatically once
   all members agree (the features_auto_finalization cluster config).
   When false, an explicit FinalizeUpgrade is required.

- **members** (array[object])
  Per-member reported version state. Compare logical_version across
   members to see whether all nodes are on the same version (ready to
   finalize) or still differ (upgrade in progress).

- **state** (string)
  High-level lifecycle state derived from the per-member versions
   below.

- **versionAfterFinalization** (integer | string)
  The active version that a FinalizeUpgrade would produce right now.
   Greater than active_version only when state is
   FINALIZATION_STATE_READY_TO_FINALIZE; otherwise equal to
   active_version (finalizing would be a no-op).


### default
Error

#### Body: application/json (object)
- **code** (string)
  The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

- **details** (array[object])
  A list of messages that carry the error details. There is no limit on the number of messages.

- **message** (string)
  A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.



[Powered by Bump.sh](https://bump.sh)