You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when create/resize volume, csi will calculate a proper capacity based on the input and some rules (e.g. hardcode or parameters in the storageclass), then call iaas. The problem is, when iaas side upgrade, csi may calculate a wrong/improper capacity.
We anticipate only and always should iaas do the capacity calculation (e.g. round up to a best available capacity), this way iaas can upgrade anytime and csi will not be affected, which is tracked by https://track.yunify.com/browse/KS-296. It seems iaas has completed the api enhancement so we can remove/disable the csi side capacity calculation.
The text was updated successfully, but these errors were encountered:
when create/resize volume, csi will calculate a proper capacity based on the input and some rules (e.g. hardcode or parameters in the storageclass), then call iaas. The problem is, when iaas side upgrade, csi may calculate a wrong/improper capacity.
We anticipate only and always should iaas do the capacity calculation (e.g. round up to a best available capacity), this way iaas can upgrade anytime and csi will not be affected, which is tracked by https://track.yunify.com/browse/KS-296. It seems iaas has completed the api enhancement so we can remove/disable the csi side capacity calculation.
The text was updated successfully, but these errors were encountered: