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

fix(vm): block connect more than 16 block devices to vm on reconcile level #495

Merged
merged 16 commits into from
Nov 11, 2024

Conversation

eofff
Copy link
Contributor

@eofff eofff commented Nov 1, 2024

Description

Do not allow connect more than 16 block devices to VM and check it in reconcilers.

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

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.

Signed-off-by: Valeriy Khorunzhin <[email protected]>
Valeriy Khorunzhin added 3 commits November 1, 2024 23:44
Signed-off-by: Valeriy Khorunzhin <[email protected]>
Signed-off-by: Valeriy Khorunzhin <[email protected]>
Signed-off-by: Valeriy Khorunzhin <[email protected]>
@eofff eofff force-pushed the fix/vm/check-block-device-limit-on-reconcile-level branch from 2b64e87 to 152337d Compare November 1, 2024 20:55
Valeriy Khorunzhin and others added 8 commits November 1, 2024 23:56
…on-reconcile-level' into fix/vm/check-block-device-limit-on-reconcile-level
Signed-off-by: Daniil Antoshin <[email protected]>
Signed-off-by: Daniil Antoshin <[email protected]>
Description
Align the method for getting the default StorageClass with how the default StorageClass is defined in k8s

Why do we need it, and what problem does it solve?
Currently if there are multiple default StorageClasses, we take the random one, the behavior in k8s is different, the last annotated default StorageClass is taken

What is the expected result?
Take the last annotated default StorageClass
Signed-off-by: Valeriy Khorunzhin <[email protected]>
@universal-itengineer universal-itengineer force-pushed the main branch 2 times, most recently from d444891 to 6e0c7e7 Compare November 6, 2024 09:13
@eofff eofff marked this pull request as ready for review November 6, 2024 13:09
@eofff eofff merged commit 394e461 into main Nov 11, 2024
1 check passed
@eofff eofff deleted the fix/vm/check-block-device-limit-on-reconcile-level branch November 11, 2024 08:37
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.

3 participants