Skip to content
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.

Sign up for GitHub

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

Jump to bottom

vsphere agents: import OVAs via the vSphere content library instead of directly to inventory #676

Open
etungsten opened this issue Nov 29, 2022 · 0 comments
Open

vsphere agents: import OVAs via the vSphere content library instead of directly to inventory #676

etungsten opened this issue Nov 29, 2022 · 0 comments
Labels
bottlerocket Testing Bottlerocket Images resource-agent Related to a resource agent component vmware

Comments

@etungsten
Copy link
Contributor

etungsten commented Nov 29, 2022 •
edited
Loading

To better support downstream users of the vmware variant of Bottlerocket, we need to make sure to test EKS-A's vSphere provisioning process as much as possible. This involves importing OVAs via vSphere content libraries through govc library.import instead of directly to the inventory through govc import.ova.

The vSphere content library apparently does additional checks against the OVA.
@etungsten etungsten added bottlerocket Testing Bottlerocket Images resource-agent Related to a resource agent component vmware labels Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bottlerocket Testing Bottlerocket Images resource-agent Related to a resource agent component vmware
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@etungsten