You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there anything in the cloud-config secret or the OSArtifact that can be set to limit the pods that spin up when building an image? The pods that spin up are not getting any memory or cpu limits applied and taking every resource they can from the host node.
I tried to set a cpu limit from what I could find in the CRD but the schema wasn't working and I couldn't create the OSArtifact.
Output of the kairos image pod taking up as much cpu as it wanted:
~$ k top pods
NAME CPU(cores) MEMORY(bytes)
hello-kairos-d8r4d 7493m 1065Mi
kairos-osbuilder-c96f9bb66-ngplp 2m 22Mi
osbuilder-nginx-744d46c789-bc9nt 0m 8Mi
My yaml manifest for the cloud config and the os artifact
Is there anything in the cloud-config secret or the OSArtifact that can be set to limit the pods that spin up when building an image? The pods that spin up are not getting any memory or cpu limits applied and taking every resource they can from the host node.
I tried to set a cpu limit from what I could find in the CRD but the schema wasn't working and I couldn't create the OSArtifact.
Output of the kairos image pod taking up as much cpu as it wanted:
My yaml manifest for the cloud config and the os artifact
The text was updated successfully, but these errors were encountered: