-
Notifications
You must be signed in to change notification settings - Fork 288
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
Get previous disk usage only from existing machine configs #6699
Get previous disk usage only from existing machine configs #6699
Conversation
74525d4
to
03689d4
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #6699 +/- ##
=======================================
Coverage 75.59% 75.60%
=======================================
Files 474 474
Lines 38250 38251 +1
=======================================
+ Hits 28916 28920 +4
+ Misses 7726 7724 -2
+ Partials 1608 1607 -1
☔ View full report in Codecov by Sentry. |
03689d4
to
56a73b5
Compare
56a73b5
to
7e4d86a
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhay-krishna The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherrypick release-0.17 |
@abhay-krishna: new pull request created: #6700 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
During upgrade of an EKS-A vSphere cluster, one of the preflight checks we do is to validate whether the cumulative disk size requirements of the
VSphereMachineConfig
s can be met by the vCenter datastore. For this, we get the previous disk size requirement for eachVSphereMachineConfig
and then add it to the value in the new cluster config, and we sum this value across allVSphereMachineConfigs
and compare it to the available space in the datastore. The previous disk usage is obtained by performing akubectl get
call on theVSphereMachineConfig
object in the old cluster, but we are also doing this for newly addedVSphereMachineConfig
which don't exist on the old cluster, which leads to errors likeWe should try to fetch the object only if the previous count of the corresponding
WorkerNodeConfiguration
is greater than 0, which indicates that theVSphereMachineConfig
exists on the old cluster.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.