Skip to content

Conversation

hardcoretime
Copy link
Contributor

@hardcoretime hardcoretime commented Jul 29, 2025

Description

Currently, only storage classes with Block volume mode and RWX access mode can be used.

Why do we need it, and what problem does it solve?

This is required until the problem with the Filesystem volume mode is resolved.

What is the expected result?

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: vi
type: chore
summary: "Currently, only storage classes with Block volume mode and RWX access mode can be used."

@hardcoretime hardcoretime force-pushed the chore/vi/validate-storage-class branch from 997b679 to 57e7fde Compare August 7, 2025 21:51
@hardcoretime hardcoretime self-assigned this Aug 7, 2025
@hardcoretime hardcoretime changed the title chore(vi): validate storage class fix(vi): validate storage class Aug 7, 2025
@hardcoretime hardcoretime added this to the v0.24.0 milestone Aug 7, 2025
@hardcoretime hardcoretime force-pushed the chore/vi/validate-storage-class branch 5 times, most recently from b179539 to 3787799 Compare August 8, 2025 07:54
Currently, only storage classes with Block volume mode and RWX access mode can be used.

Signed-off-by: Roman Sysoev <[email protected]>
@hardcoretime hardcoretime force-pushed the chore/vi/validate-storage-class branch from 3787799 to 7d64743 Compare August 8, 2025 08:34
@hardcoretime hardcoretime added the e2e/run Run e2e test on cluster of PR author label Aug 8, 2025
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Aug 8, 2025

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Aug 8, 2025
@hardcoretime hardcoretime added the e2e/run Run e2e test on cluster of PR author label Aug 8, 2025
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Aug 8, 2025

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: success.

@universal-itengineer universal-itengineer modified the milestones: v0.24.0, v0.25.0 Aug 8, 2025
@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Aug 8, 2025
@hardcoretime hardcoretime marked this pull request as ready for review August 8, 2025 12:22
@hardcoretime hardcoretime requested a review from diafour August 8, 2025 13:10
@hardcoretime hardcoretime requested a review from diafour August 11, 2025 11:43
@hardcoretime hardcoretime added the e2e/run Run e2e test on cluster of PR author label Aug 11, 2025
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Aug 11, 2025

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Aug 11, 2025
@hardcoretime hardcoretime added the e2e/run Run e2e test on cluster of PR author label Aug 11, 2025
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Aug 11, 2025

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Aug 11, 2025
Copy link
Member

@diafour diafour left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@hardcoretime hardcoretime merged commit 637ae52 into main Aug 12, 2025
74 of 76 checks passed
@hardcoretime hardcoretime deleted the chore/vi/validate-storage-class branch August 12, 2025 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants