Skip to content

csi: handle spec updates for volume health - #28474

Draft
chrisroberts wants to merge 1 commit into
mainfrom
f-csi-volume-health
Draft

csi: handle spec updates for volume health#28474
chrisroberts wants to merge 1 commit into
mainfrom
f-csi-volume-health

Conversation

@chrisroberts

Copy link
Copy Markdown
Member

Description

The condition of a volume is no longer reported within the status information returned in the list volume response. Instead, an endpoint now exists to query the volume health. The new endpoint is now used to include the condition of the volume if it is available.

Like the previous volume condition field, the volume health endpoint is considered alpha within the spec and may be removed or modified in the future.

Removal of volume condition and addition of volume health: ref

Testing & Reproduction steps

Links

Contributor Checklist

  • Changelog Entry If this PR changes user-facing behavior, please generate and add a
    changelog entry using the make cl command.
  • Testing Please add tests to cover any new functionality or to demonstrate bug fixes and
    ensure regressions will be caught.
  • Documentation If the change impacts user-facing functionality such as the CLI, API, UI,
    and job configuration, please update the Nomad product documentation, which is stored in the
    web-unified-docs repo. Refer to the web-unified-docs contributor guide for docs guidelines.
    Please also consider whether the change requires notes within the upgrade
    guide
    . If you would like help with the docs, tag the nomad-docs team in this PR.
  • LLM Usage If an LLM was used to generate any code, please ensure and confirm you have read
    and followed the AI usage guide.

Reviewer Checklist

  • Backport Labels Please add the correct backport labels as described by the internal
    backporting document.
  • Commit Type Ensure the correct merge method is selected which should be "squash and merge"
    in the majority of situations. The main exceptions are long-lived feature branches or merges where
    history should be preserved.
  • Enterprise PRs If this is an enterprise only PR, please add any required changelog entry
    within the public repository.
  • If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

@chrisroberts chrisroberts added backport/ent/1.10.x+ent backport to 1.10.x+ent release line backport/ent/1.11.x+ent backport to 1.11.x+ent release line backport/2.0.x backport to 2.0.x release line labels Sep 2, 2026
The condition of a volume is no longer reported within the status
information returned in the list volume response. Instead, an
endpoint now exists to query the volume health. The new endpoint
is now used to include the condition of the volume if it is
available.

Like the previous volume condition field, the volume health
endpoint is considered alpha within the spec and may be removed
or modified in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/ent/1.10.x+ent backport to 1.10.x+ent release line backport/ent/1.11.x+ent backport to 1.11.x+ent release line backport/2.0.x backport to 2.0.x release line

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant