How to run on TKGm #16
Comments
|
Not at the moment, but this is something we want to do in the future with vm-operator. |
|
Any updates on when and if this will be possible? |
|
No updates at the moment. |
akutz
pushed a commit
that referenced
this issue
Nov 19, 2022
OvfEnv is a standard way to transport key/value vm customization data from the infrastructure to the VM, as well as exposing them to guest os/apps within the VM. Possible key/value properties that are userConfigurable would be already defined in the .ovf image as defined in the OVF Spec 2.1.1 Section 11 https://www.dmtf.org/sites/default/files/standards/documents/DSP0243_2.1.1.pdf This MR makes it possible to supply key/value fields to set the userConfigurable property fields on a .ovf during the VirtualMachine create time. The VirtualMachine spec already has a VmMetadata field which already supports a "ExtraConfig" transport, and this change adds another possible transport which is "OvfEnv".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
is it possible to run the vm operator on a TKGm cluster or any K8s cluster except for a supervisor cluster?
if it is possible what is the process?
The text was updated successfully, but these errors were encountered: