This repository has been archived by the owner on Sep 7, 2022. It is now read-only.
forked from kubernetes/kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 31
Validate all container host OSes against Virtual hardware version 13 #450
Comments
tusharnt
changed the title
Validate all Container host OSes against VMX13 onwards
Validate all Container host OSes against VMX13 & onwards
Feb 1, 2018
tusharnt
changed the title
Validate all Container host OSes against VMX13 & onwards
Validate all container host OSes against VMX13 & onwards
Feb 1, 2018
This was referenced Feb 1, 2018
Here is my observations. VM version 13
VM version 11
CC: @SandeepPissay |
tusharnt
changed the title
Validate all container host OSes against VMX13 & onwards
Validate all container host OSes against Virtual hardware version 13
Feb 2, 2018
As we discussed, let us use product_serial in the OS and use that for discovering the node. Since this always matches the VM's uuid in VC inventory, the discovery will be successful. |
This needs to be cherry-picked to 1.9. |
Cherrypicked to 1.9 here |
Documentation PR and Cherrypick PR is merged. The fix is available in k8s v1.9.4 |
This was referenced Mar 4, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Validate all container host OSes against Virtual Hardware version 13 and update customer facing documentation.
Fix VCP issues uncovered if any.
The text was updated successfully, but these errors were encountered: