From ae7bff67c911ad8d307190dfc3692114da881396 Mon Sep 17 00:00:00 2001 From: Em Sharnoff Date: Fri, 6 Dec 2024 08:04:38 -0800 Subject: [PATCH] neonvm: Bump max mem slots to 512 In practice this is limiting the maximum size of our computes, even though memory slots aren't physically used since we switched to virtio-mem. ref neondatabase/cloud#18281 --- neonvm/apis/neonvm/v1/virtualmachine_types.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/neonvm/apis/neonvm/v1/virtualmachine_types.go b/neonvm/apis/neonvm/v1/virtualmachine_types.go index 9e93f36ac..b44abacca 100644 --- a/neonvm/apis/neonvm/v1/virtualmachine_types.go +++ b/neonvm/apis/neonvm/v1/virtualmachine_types.go @@ -413,15 +413,15 @@ func (m MilliCPU) Format(state fmt.State, verb rune) { type MemorySlots struct { // +kubebuilder:validation:Minimum=1 - // +kubebuilder:validation:Maximum=128 + // +kubebuilder:validation:Maximum=512 // +kubebuilder:validation:ExclusiveMaximum=false Min int32 `json:"min"` // +kubebuilder:validation:Minimum=1 - // +kubebuilder:validation:Maximum=128 + // +kubebuilder:validation:Maximum=512 // +kubebuilder:validation:ExclusiveMaximum=false Max int32 `json:"max"` // +kubebuilder:validation:Minimum=1 - // +kubebuilder:validation:Maximum=128 + // +kubebuilder:validation:Maximum=512 // +kubebuilder:validation:ExclusiveMaximum=false Use int32 `json:"use"` }