Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[controller] Fixed default Storage Class validation #32

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

duckhawk
Copy link
Member

@duckhawk duckhawk commented Apr 22, 2024

Description

Fixed default Storage Class validation

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

Now default storage class validation working incorrect

What is the expected result?

Correct storage class validation

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.

@duckhawk duckhawk requested a review from AleksZimin April 22, 2024 11:47
@duckhawk duckhawk added the enhancement New feature or request label Apr 22, 2024
@duckhawk duckhawk self-assigned this Apr 22, 2024
@duckhawk duckhawk force-pushed the correct-default-sc-validation branch from 8b8b110 to 882e9af Compare April 22, 2024 12:15
@duckhawk duckhawk marked this pull request as ready for review April 22, 2024 13:10
Signed-off-by: v.oleynikov <vasily.oleynikov@flant.com>
@duckhawk duckhawk force-pushed the correct-default-sc-validation branch from fe51cc4 to f266c6f Compare April 22, 2024 13:11
@AleksZimin AleksZimin changed the title Fixed default Storage Class validation [controller] Fixed default Storage Class validation Apr 23, 2024
@AleksZimin AleksZimin merged commit f9de0c3 into main Apr 23, 2024
3 checks passed
@AleksZimin AleksZimin deleted the correct-default-sc-validation branch April 23, 2024 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants