OSBuilder Issues

[ndlanier]

I have a couple of issues with OSBuilder. Currently deployed on a gke cluster, and have tested using a local k3s baremetal cluster.

1. The image pods that spawn from the osbuilder eat up all the available CPU on the node (see Set CPU limits for pods for kairos image build pods osbuilder#87). Is there any way to add cpu and memory limits to the OSArtifact or in the cloud config?
2. Once OSBuilder completes on a cloud image, I am not getting the resulting artifact to show up on the server, a lost+found directory gets created but it's empty. I check the logs for the pods and there are no errors reported, same for the pod events. There definitely needs to be a little more of verbose output to the logs on what exactly is going on. Has anyone run into this issue by chance? (Submitted an issue: Artifact is missing despite logs saying it was successfully created osbuilder#89)

[ndlanier]

Figured out the image export issue, should have just read the note from the helm chart haha.

I have found that resource limits weren't accounted for OSArtifacts pods. I've looked in the osartifact_types.go and the contollers go files and don't see anything for setting resource limits.