Skip to content

Conversation

@walkafwalka
Copy link

@walkafwalka walkafwalka commented Jul 21, 2025

Issue: #1030

Problem

vGPUs parameter is not supported in the Harvester config for the Machine Config resource.

Solution

Adds support for the vGPU parameter.

Testing

Specify a vgpu_info parameter and check that it is populated in the HarvesterConfig.

Engineering Testing

Manual Testing

Currently using this fork in our environment.

Automated Testing

QA Testing Considerations

Regressions Considerations

@walkafwalka walkafwalka force-pushed the machine-config-harvester-vgpu branch 2 times, most recently from 7020d40 to d9d10af Compare July 21, 2025 19:39
@walkafwalka
Copy link
Author

@matttrach Any bandwidth to look into this?

@walkafwalka walkafwalka force-pushed the machine-config-harvester-vgpu branch from eb750f4 to bd1b52f Compare August 14, 2025 20:58
@walkafwalka walkafwalka force-pushed the machine-config-harvester-vgpu branch from bd1b52f to 7339baf Compare August 14, 2025 20:59
@ibrokethecloud ibrokethecloud requested review from Vicente-Cheng and removed request for Vicente-Cheng September 4, 2025 10:06
Copy link
Member

@m-ildefons m-ildefons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a fan of letting users input JSON strings directly. Especially if there isn't ample documentation about the expected schema and other information available to users.

The vGPU information should be a subresource and the Terrafrom provider should marshall the user input into JSON automatically.
This lets us apply a wide variety of validation and makes it more user friendly, because the expected schema of the user input is better documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants