Update min*Mem constants to use MiB instead of MB #9180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At some point, minikube changed from MB to MiB internally, but the constants were never updated.
This fixes the confusing behavior when a user sets Docker to 2GB (1907MiB), but we still warn because it is less than 2000.
This also fixes it so that minikube does not force exit if Docker is set to 1GB of RAM (953MiB), which is acceptable enough for Kubernetes, leaving 200MiB to spare.