> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Get Edge-Node Cluster raw status. > GET /api/v1/cluster/id/{id}/raw/status. Edge node clusters API reference. Sign in to try this endpointExplore the parameters, examples, and responses below. Connect your ZedCloud session when you’re ready to send a request. > [accordion] Connect your console > > Sign in to your usual ZedCloud console, then open: > >
    >
  1. Profile menu
  2. Help & Documentation
  3. API Reference
    4. >
> > Your cluster and authorization are filled in automatically. No token to copy. > [More about signing in ](https://zededa.mintlify.site/api-reference/authentication.md#sign-in-to-the-api-reference) Modifying requests stay off until you enable them. [Authentication](https://zededa.mintlify.site/api-reference/authentication.md) · [API availability](https://zededa.mintlify.site/api-reference/clusters.md) · [Download OpenAPI](https://zededa.mintlify.site/openapi/services/edge-node-cluster.json) A successful response. Bad Request. The API gateway did not process the request because of missing parameter or invalid value of parameters. Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused. Forbidden. The API gateway did not process the request because the requestor does not have application level access permission for the operation or does not have access scope to the project. Not Found. The API gateway did not process the request because the requested resource could not be found. Conflict. The API gateway did not process the request because this edge-node cluster record will conflict with an already existing edge-node cluster record. Precondition failed. Some of preconditions haven't been met to start request processing. Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes. Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request. An unexpected error response. ## OpenAPI ````yaml openapi/services/edge-node-cluster.json GET /v1/cluster/id/{id}/raw/status openapi: 3.0.0 info: title: ZEDEDA Edge-Node Cluster Service description: >- The service defines the APIs to work with edge-node clusters. The APIs include such operations as creating, updating, and deleting edge-node clusters, as well as listing and getting details of edge-node clusters. termsOfService: https://www.zededa.com/terms version: '1.0' contact: name: ZEDEDA API Support url: https://www.zededa.com/support email: support@zededa.com license: name: Apache 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://{apiHost}/api variables: apiHost: default: invalid.invalid description: Connect from ZedUI to supply your verified API destination. security: - BearerToken: [] tags: - name: EdgeNodeClusterConfiguration - name: ClusterStatus externalDocs: description: ZEDEDA Product Documentation url: https://help.zededa.com/ paths: /v1/cluster/id/{id}/raw/status: get: tags: - ClusterStatus summary: Get Edge-Node Cluster raw status. description: >- Get the raw (unprocessed) status of an Edge-Node Cluster as reported by the cluster reporter. operationId: ClusterStatus_GetClusterRawStatus parameters: - name: id description: System defined universally unique Id of the cluster in: path required: true schema: type: string - name: X-Request-Id in: header required: false description: User-Agent specified id to track a request schema: type: string responses: '200': description: A successful response. content: application/json: schema: $ref: '#/components/schemas/EdgeNodeClusterRawInfo' '400': description: >- Bad Request. The API gateway did not process the request because of missing parameter or invalid value of parameters. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '401': description: >- Unauthorized. The API gateway did not process the request because it lacks valid authentication credentials for the target resource. The request header has either no authorization details or an authorization that has been refused. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '403': description: >- Forbidden. The API gateway did not process the request because the requestor does not have application level access permission for the operation or does not have access scope to the project. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '404': description: >- Not Found. The API gateway did not process the request because the requested resource could not be found. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '409': description: >- Conflict. The API gateway did not process the request because this edge-node cluster record will conflict with an already existing edge-node cluster record. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '412': description: >- Precondition failed. Some of preconditions haven't been met to start request processing. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '500': description: >- Internal Server Error. The API gateway experienced an unexpected condition. Specific error condition is indicated in error codes. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' '504': description: >- Gateway Timeout. The API gateway did not receive a timely response from an upstream microservice it needed to communicate with in order to complete the request. content: application/json: schema: $ref: '#/components/schemas/ZsrvResponse' default: description: An unexpected error response. content: application/json: schema: $ref: '#/components/schemas/googlerpcStatus' externalDocs: description: ZEDEDA Product Documentation url: https://help.zededa.com components: schemas: EdgeNodeClusterRawInfo: type: object properties: cluster: $ref: '#/components/schemas/infoZInfoKubeCluster' upgradeStatus: $ref: '#/components/schemas/infoZInfoKubeClusterUpdateStatus' ZsrvResponse: type: object properties: operationType: title: |- Describes one of the operations type : possible values Read/Delete/Create/Update/List allOf: - $ref: '#/components/schemas/ZcOpsType' operationStatus: title: if this is log running job allOf: - $ref: '#/components/schemas/ZcOpsStatus' objectKind: type: string title: zedcloud object kind on which the operation was performed objectId: type: string title: Unique value identifies the object that was operated on objectName: type: string title: name of the object objectRevision: type: string title: |- object revision post the operation, note Read operation doesn't change the revision objectType: $ref: '#/components/schemas/ObjectType' operationTime: type: string title: time of operation startTime: type: string title: total time taken by operations endTime: type: string user: type: string title: the operation is performed on behalf of this user httpStatusCode: type: integer format: int32 title: http response httpStatusMsg: type: string title: summary of the error in text format jobId: type: string title: for tracking asynchronous tasks error: type: array items: $ref: '#/components/schemas/ZsrvError' title: |- one or more errors will be set if the operation failed i.e. httpStatusCode != 2xx googlerpcStatus: type: object properties: code: type: integer format: int32 message: type: string details: type: array items: $ref: '#/components/schemas/protobufAny' infoZInfoKubeCluster: type: object properties: nodes: type: array items: $ref: '#/components/schemas/infoKubeNodeInfo' title: Info message on a list of cluster nodes podNameSpaces: type: array items: $ref: '#/components/schemas/infoKubePodNameSpaceInfo' title: Info message on a list of namespaces's pods summary eveApps: type: array items: $ref: '#/components/schemas/infoKubeEVEAppPodInfo' title: Info message on a list of EVE applications storage: title: Info message on cluster storage allOf: - $ref: '#/components/schemas/infoKubeStorageInfo' clusterId: type: string description: >- Cluster UUID which will match config.EdgeNodeCluster.cluster_id passed in to the node by the controller. eveVmApps: type: array items: $ref: '#/components/schemas/infoKubeVMIInfo' title: Virtual Machines running on the cluster infoZInfoKubeClusterUpdateStatus: type: object properties: currentNode: type: string title: current_node will have an empty value when no node is in an update component: title: >- component currently under update or KUBE_COMP_UNSPECIFIED when no update in progress allOf: - $ref: '#/components/schemas/infoKubeComp' status: title: >- status of the current component under update, KUBE_COMP_UPDATE_STATUS_UNSPECIFIED when no updates in progress allOf: - $ref: '#/components/schemas/infoKubeCompUpdateStatus' error: title: Error info in case of failure allOf: - $ref: '#/components/schemas/infoErrorInfo' clusterId: type: string description: >- Cluster UUID which will match config.EdgeNodeCluster.cluster_id passed in to the node by the controller. ZcOpsType: type: string enum: - OPS_TYPE_UNSPECIFIED - OPS_TYPE_READ - OPS_TYPE_DELETE - OPS_TYPE_CREATE - OPS_TYPE_UPDATE - OPS_TYPE_LIST default: OPS_TYPE_UNSPECIFIED title: ZedCloud internal operation type ZcOpsStatus: type: string enum: - OPS_STATUS_UNSPECIFIED - OPS_STATUS_PENDING - OPS_STATUS_ONGOING - OPS_STATUS_COMPLETE default: OPS_STATUS_UNSPECIFIED description: >- - OPS_STATUS_PENDING: In rare cases, system may not start operation when it was requested. Client will be notified that operation is PENDING - OPS_STATUS_ONGOING: system will start the operation, but at the time response was generated, operation is still ONGOING. - OPS_STATUS_COMPLETE: Even if the result of the operations may result in failure, but the OpsStatus will marked COMPLETE for almost all cases. title: ZedCloud internal operation status ObjectType: type: string enum: - OBJECT_TYPE_UNSPECIFIED - OBJECT_TYPE_USER - OBJECT_TYPE_EDGE_NODE - OBJECT_TYPE_EDGE_APP - OBJECT_TYPE_IMAGE - OBJECT_TYPE_EDGE_APP_INSTANCE - OBJECT_TYPE_PROJECT - OBJECT_TYPE_NETWORK - OBJECT_TYPE_DATASTORE - OBJECT_TYPE_SERVICE - OBJECT_TYPE_SERVICE_INSTANCE - OBJECT_TYPE_ENTERPRISE - OBJECT_TYPE_ROLE - OBJECT_TYPE_CREDENTIAL - OBJECT_TYPE_NETWORK_INSTANCE - OBJECT_TYPE_VOLUME_INSTANCE - OBJECT_TYPE_REALM - OBJECT_TYPE_AUTHPROFILE - OBJECT_TYPE_POLICY - OBJECT_TYPE_APP_POLICY - OBJECT_TYPE_CLUSTER_INSTANCE - OBJECT_TYPE_PLUGIN - OBJECT_TYPE_DOC_POLICY - OBJECT_TYPE_ORCHESTRATOR_CLUSTER - OBJECT_TYPE_TAGS - OBJECT_TYPE_EDGE_NODE_INTERFACE - OBJECT_TYPE_DEPLOYMENT - OBJECT_TYPE_ENTITLEMENTS - OBJECT_TYPE_DATA_STREAM - OBJECT_TYPE_API_USAGE - OBJECT_TYPE_APP_INSTANCE_SNAPSHOT - OBJECT_TYPE_PATCH_ENVELOPE - OBJECT_TYPE_RESOURCE_USAGE_TRACK - OBJECT_TYPE_PATCH_ENVELOPE_REFERENCE - OBJECT_TYPE_DEV_PASSTHROUGH - OBJECT_TYPE_EDGE_NODE_CLUSTER - OBJECT_TYPE_ASSET_GROUP - OBJECT_TYPE_APP_PROFILE - OBJECT_TYPE_PROFILE_DEPLOYMENT - OBJECT_TYPE_ZKS_INSTANCE - OBJECT_TYPE_CLUSTER_GROUP default: OBJECT_TYPE_UNSPECIFIED ZsrvError: type: object properties: ec: title: |- Enumrated error code, describes more granular numerical value than just httpStatus allOf: - $ref: '#/components/schemas/ZsrvErrorCode' location: type: string title: 'Ignore: Internal field only' details: type: string title: Field captures string description of details protobufAny: type: object properties: typeUrl: type: string value: type: string format: byte infoKubeNodeInfo: type: object properties: name: type: string title: Name of the node, will match device name conditions: type: array items: $ref: '#/components/schemas/infoKubeNodeCondition' title: Status of the node roleServer: type: boolean title: Role of the node is server or not creationTimestamp: type: string format: date-time title: Creation Time of the node in the cluster apiServerSersion: type: string title: Version of the API Server running on the node internalIp: type: string title: Internal IP address of the node schedulable: type: boolean admissionStatus: title: Admission State of the local node in a cluster allOf: - $ref: '#/components/schemas/infoNodeAdmission' nodeId: type: string title: Id of the eve node matching config.EdgeDevConfig.id infoKubePodNameSpaceInfo: type: object properties: name: type: string title: Name of the namespace podCount: type: integer format: int64 title: Number of pods in the namespace podRunningCount: type: integer format: int64 title: Number of pods in the namespace that are running podPendingCount: type: integer format: int64 title: Number of pods in the namespace that are pending podFailedCount: type: integer format: int64 title: Number of pods in the namespace that are failed podSucceededCount: type: integer format: int64 title: Number of pods in the namespace that are succeeded infoKubeEVEAppPodInfo: type: object properties: name: type: string title: Name of the EVE application status: title: Application Status allOf: - $ref: '#/components/schemas/infoKubePodStatus' restartCount: type: integer format: int64 title: Restart count of the application restartTimestamp: type: string format: date-time title: Restart time of the application creationTimestamp: type: string format: date-time title: Creation Time of the application ipAddress: type: string title: IP address of the application, on cni0 interface nodeName: type: string title: Node name on which the application is running infoKubeStorageInfo: type: object properties: health: title: Health of the distributes storage services allOf: - $ref: '#/components/schemas/infoServiceStatus' transitionTime: type: string format: date-time title: Time of the most recent health status transition volumes: type: array items: $ref: '#/components/schemas/infoKubeVolumeInfo' title: Status of all the volumes in Longhorn infoKubeVMIInfo: type: object properties: name: type: string title: Name of the VirtualMachineInstance status: title: Status (VirtualMachineInstance.Status.Phase) allOf: - $ref: '#/components/schemas/infoKubeVMIStatus' creationTime: type: string format: date-time title: Creation Time of the VirtualMachineInstance lastTransitionTime: type: string format: date-time title: LastTransitionTime is the last time is_ready changed isReady: type: boolean title: IsReady is true if the VMI has a Ready Condition which is true nodeName: type: string title: >- NodeName is the current node (kubernetes.io/hostname) the VMI is running on title: KubeVMIInfo is the VMI status of eve VM apps infoKubeComp: type: string enum: - KUBE_COMP_UNSPECIFIED - KUBE_COMP_CONTAINERD - KUBE_COMP_K3S - KUBE_COMP_MULTUS - KUBE_COMP_KUBEVIRT - KUBE_COMP_CDI - KUBE_COMP_LONGHORN default: KUBE_COMP_UNSPECIFIED description: |- KubeComp is a component installed in eve after usb install. These are provided to show more detail on cluster update progress. infoKubeCompUpdateStatus: type: string enum: - KUBE_COMP_UPDATE_STATUS_UNSPECIFIED - KUBE_COMP_UPDATE_STATUS_DOWNLOAD - KUBE_COMP_UPDATE_STATUS_DOWNLOAD_FAILED - KUBE_COMP_UPDATE_STATUS_IN_PROGRESS - KUBE_COMP_UPDATE_STATUS_FAILED - KUBE_COMP_UPDATE_STATUS_COMPLETED default: KUBE_COMP_UPDATE_STATUS_UNSPECIFIED description: |- KubeCompUpdateStatus will track status of each KubeComp which will update serially in a cluster. infoErrorInfo: type: object properties: description: type: string timestamp: type: string format: date-time severity: $ref: '#/components/schemas/eveinfoSeverity' entities: type: array items: $ref: '#/components/schemas/eveinfoDeviceEntity' retryCondition: type: string description: >- Describes an error that occurred while applying a configuration to the device. ZsrvErrorCode: type: string enum: - zMsgErrorNone - zMsgSucess - NotFound - AlreadyExists - VersionMismatch - RangeError - LargeResult - IncompleteData - InvalidData - FunctionUnsupported - NoMemory - SendFailure - Timeout - BadReqBody - BadReqParam - InvalidFieldFormat - UrlNotFound - ApiVersionNotSupported - Unauthorized - Forbidden - Conflict - NotModified - DependencyConflict - JsonFmtError - ProtoFmtError - CertError - DataBaseConnection - DBError - zMsgAccepted - zMsgCreated - PreConditionFailed - InternalServerError default: zMsgErrorNone description: |- - zMsgErrorNone: common validation errors - IncompleteData: message had fields that weren't filled in - InvalidData: message contained the field that wasn't expected - FunctionUnsupported: this feature unavailable on this version of device - InvalidFieldFormat: message contained the field that wasn't correctly formatted - JsonFmtError: Marshal / Unmarshal errors - DataBaseConnection: generic DB error title: ZedCould internal error code infoKubeNodeCondition: type: object properties: type: title: Type of the condition allOf: - $ref: '#/components/schemas/infoKubeNodeConditionType' set: type: boolean title: Condition state lastTransitionTime: type: string format: date-time title: last_transition_time is the last time the Condition changed infoNodeAdmission: type: string enum: - NODE_ADMISSION_UNSPECIFIED - NODE_ADMISSION_NOT_CLUSTERED - NODE_ADMISSION_LEAVING - NODE_ADMISSION_JOINING - NODE_ADMISSION_JOINED default: NODE_ADMISSION_UNSPECIFIED description: >- - NODE_ADMISSION_NOT_CLUSTERED: Not Clustered is the default state at first boot - NODE_ADMISSION_LEAVING: Leaving can be a long lived state due to draining existing data - NODE_ADMISSION_JOINING: Joining can be a long lived state if inter-node networking is not operable - NODE_ADMISSION_JOINED: Joined is reached when the node becomes Ready the first time after a request to join the cluster title: Cluster Admission status of the eve node infoKubePodStatus: type: string enum: - KUBE_POD_STATUS_UNSPECIFIED - KUBE_POD_STATUS_PENDING - KUBE_POD_STATUS_RUNNING - KUBE_POD_STATUS_SUCCEEDED - KUBE_POD_STATUS_CONTAINER_CREATING - KUBE_POD_STATUS_CRASHLOOP_BACKOFF - KUBE_POD_STATUS_ERROR - KUBE_POD_STATUS_EVICTED - KUBE_POD_STATUS_FAILED default: KUBE_POD_STATUS_UNSPECIFIED title: |- KubePodStatus is a combination of the kubernetes status: PodPhase: https://pkg.go.dev/k8s.io/api/core/v1#PodPhase PodConditionType: https://pkg.go.dev/k8s.io/api/core/v1#PodConditionType ContainerState: https://pkg.go.dev/k8s.io/api/core/v1#ContainerState infoServiceStatus: type: string enum: - SERVICE_STATUS_UNSPECIFIED - SERVICE_STATUS_FAILED - SERVICE_STATUS_DEGRADED - SERVICE_STATUS_HEALTHY default: SERVICE_STATUS_UNSPECIFIED title: |- ServiceStatus denotes a cluster wide infrastructure component's health. eg. a daemonset which requires pods on multiple nodes infoKubeVolumeInfo: type: object properties: name: type: string title: Name of the volume state: title: Status of the volume attachment allOf: - $ref: '#/components/schemas/infoStorageVolumeState' robustness: title: Robustness of the volume allOf: - $ref: '#/components/schemas/infoStorageVolumeRobustness' creationTimestamp: type: string format: date-time title: Creation Time of the volume in the cluster provisionedBytes: type: string format: uint64 title: Provisioned size of the volume in bytes allocatedBytes: type: string format: uint64 title: Allocated size of the volume in bytes pvcStatus: title: PV/PVC status of the volume allOf: - $ref: '#/components/schemas/infoStorageVolumePVCStatus' replica: type: array items: $ref: '#/components/schemas/infoKubeVolumeReplicaInfo' title: Replicas of the volume robustnessSubstate: title: Robustness substate of the replication status of the volume allOf: - $ref: '#/components/schemas/infoStorageHealthStatus' volumeId: type: string title: Id of the eve volume info.ZInfoVolume.uuid infoKubeVMIStatus: type: string enum: - KUBE_VMI_STATUS_UNSPECIFIED - KUBE_VMI_STATUS_PENDING - KUBE_VMI_STATUS_SCHEDULING - KUBE_VMI_STATUS_SCHEDULED - KUBE_VMI_STATUS_RUNNING - KUBE_VMI_STATUS_SUCCEEDED - KUBE_VMI_STATUS_FAILED - KUBE_VMI_STATUS_UNKNOWN default: KUBE_VMI_STATUS_UNSPECIFIED title: >- KubeVMIStatus is the VirtualMachineInstancePhase Refer to: https://pkg.go.dev/kubevirt.io/api/core/v1#VirtualMachineInstancePhase eveinfoSeverity: type: string enum: - SEVERITY_UNSPECIFIED - SEVERITY_NOTICE - SEVERITY_WARNING - SEVERITY_ERROR default: SEVERITY_UNSPECIFIED title: Severity tells the severity type eveinfoDeviceEntity: type: object properties: entity: $ref: '#/components/schemas/eveinfoEntity' entityId: type: string entityName: type: string title: DeviceEntity contains the device entity details infoKubeNodeConditionType: type: string enum: - KUBE_NODE_CONDITION_TYPE_UNSPECIFIED - KUBE_NODE_CONDITION_TYPE_READY - KUBE_NODE_CONDITION_TYPE_MEMORY_PRESSURE - KUBE_NODE_CONDITION_TYPE_DISK_PRESSURE - KUBE_NODE_CONDITION_TYPE_PID_PRESSURE - KUBE_NODE_CONDITION_TYPE_NETWORK_UNAVAIL default: KUBE_NODE_CONDITION_TYPE_UNSPECIFIED title: |- KubeNodeStatus follows Kubernetes Node Conditions Refer here: https://pkg.go.dev/k8s.io/api/core/v1#NodeConditionType infoStorageVolumeState: type: string enum: - STORAGE_VOLUME_STATE_UNSPECIFIED - STORAGE_VOLUME_STATE_CREATING - STORAGE_VOLUME_STATE_ATTACHED - STORAGE_VOLUME_STATE_DETACHED - STORAGE_VOLUME_STATE_ATTACHING - STORAGE_VOLUME_STATE_DETACHING - STORAGE_VOLUME_STATE_DELETING default: STORAGE_VOLUME_STATE_UNSPECIFIED title: >- StorageVolumeState is the kubernetes 'state' field of a replicated csi-driver volume. Refer to: https://github.com/longhorn/longhorn-manager/blob/v1.6.2/k8s/pkg/apis/longhorn/v1beta1/volume.go#L14 infoStorageVolumeRobustness: type: string enum: - STORAGE_VOLUME_ROBUSTNESS_UNSPECIFIED - STORAGE_VOLUME_ROBUSTNESS_HEALTHY - STORAGE_VOLUME_ROBUSTNESS_DEGRADED - STORAGE_VOLUME_ROBUSTNESS_FAULTED default: STORAGE_VOLUME_ROBUSTNESS_UNSPECIFIED title: >- StorageVolumeRobustness is the 'robustness' of a replicated csi-driver volume. Refer to: https://github.com/longhorn/longhorn-manager/blob/v1.6.2/k8s/pkg/apis/longhorn/v1beta1/volume.go#L25 infoStorageVolumePVCStatus: type: string enum: - STORAGE_VOLUME_PVC_STATUS_UNSPECIFIED - STORAGE_VOLUME_PVC_STATUS_BOUND - STORAGE_VOLUME_PVC_STATUS_PENDING - STORAGE_VOLUME_PVC_STATUS_AVAILABLE - STORAGE_VOLUME_PVC_STATUS_RELEASED - STORAGE_VOLUME_PVC_STATUS_FAILED default: STORAGE_VOLUME_PVC_STATUS_UNSPECIFIED title: >- StorageVolumePVCStatus is the kubernetes 'phase' of a PVC. Listed as status in cli. Refer to: https://kubernetes.io/docs/concepts/storage/persistent-volumes#phase infoKubeVolumeReplicaInfo: type: object properties: name: type: string title: Name of the volume replica ownerNode: type: string title: Node replica resides on, will match node name rebuildProgressPercentage: type: integer format: int64 title: Rebuild progress of the volume replica status: title: Replica status allOf: - $ref: '#/components/schemas/infoStorageVolumeReplicaStatus' infoStorageHealthStatus: type: string enum: - STORAGE_HEALTH_STATUS_UNSPECIFIED - STORAGE_HEALTH_STATUS_HEALTHY - STORAGE_HEALTH_STATUS_DEGRADED_2_REPLICA_AVAILABLE_REPLICATING - STORAGE_HEALTH_STATUS_DEGRADED_2_REPLICA_AVAILABLE_NOT_REPLICATING - STORAGE_HEALTH_STATUS_DEGRADED_1_REPLICA_AVAILABLE_REPLICATING - STORAGE_HEALTH_STATUS_DEGRADED_1_REPLICA_AVAILABLE_NOT_REPLICATING - STORAGE_HEALTH_STATUS_FAILED default: STORAGE_HEALTH_STATUS_UNSPECIFIED description: >- StorageHealthStatus is a higher level tracking status to show redundancy/failure-zone level and rebuild progress. eveinfoEntity: type: string enum: - ENTITY_UNSPECIFIED - ENTITY_BASE_OS - ENTITY_SYSTEM_ADAPTER - ENTITY_VAULT - ENTITY_ATTESTATION - ENTITY_APP_INSTANCE - ENTITY_PORT - ENTITY_NETWORK - ENTITY_NETWORK_INSTANCE - ENTITY_CONTENT_TREE - ENTITY_CONTENT_BLOB - ENTITY_VOLUME default: ENTITY_UNSPECIFIED description: |- - ENTITY_UNSPECIFIED: Invalid Device Entity - ENTITY_BASE_OS: Base OS entity - ENTITY_SYSTEM_ADAPTER: System Adapter Entity - ENTITY_VAULT: Vault Entity - ENTITY_ATTESTATION: Attestation Entity - ENTITY_APP_INSTANCE: App Instance Entity - ENTITY_PORT: Port Entity - ENTITY_NETWORK: Network Entity - ENTITY_NETWORK_INSTANCE: Network Instance Entity - ENTITY_CONTENT_TREE: ContentTree Entity - ENTITY_CONTENT_BLOB: Blob Entity - ENTITY_VOLUME: VOLUME Entity title: Entity contains the entity type infoStorageVolumeReplicaStatus: type: string enum: - STORAGE_VOLUME_REPLICA_STATUS_UNSPECIFIED - STORAGE_VOLUME_REPLICA_STATUS_REBUILDING - STORAGE_VOLUME_REPLICA_STATUS_ONLINE - STORAGE_VOLUME_REPLICA_STATUS_FAILED - STORAGE_VOLUME_REPLICA_STATUS_OFFLINE - STORAGE_VOLUME_REPLICA_STATUS_STARTING - STORAGE_VOLUME_REPLICA_STATUS_STOPPING default: STORAGE_VOLUME_REPLICA_STATUS_UNSPECIFIED description: >- StorageVolumeReplicaStatus is a higher level status which combines replica and engine status to show a simplified view of a replica rebuild state. securitySchemes: BearerToken: type: http description: Bearer token for user session scheme: bearer ````