From 4315e50491d0c624df3c37ffcc54e1f974d2ea19 Mon Sep 17 00:00:00 2001
From: Andrew Quinn <146476524+AndrewMRQuinn@users.noreply.github.com>
Date: Tue, 23 Dec 2025 12:52:51 +0000
Subject: [PATCH] Accept int for StatefulSet maxUnavailable

The maxUnavailable field is available for StatefulSets by default as of Kubernetes v1.35, and defaults to an integer value of 1.
https://kubernetes.io/blog/2025/12/17/kubernetes-v1-35-release/#maxunavailable-for-statefulsets

The StatefulSetRollingUpdate class only accepted a string value, resulting in a validation error after updating to Kubernetes v1.35.

The change allows an integer or a string, matching the RollingUpdate class.
---
 packages/cmk-plugins/cmk/plugins/kube/schemata/api.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/cmk-plugins/cmk/plugins/kube/schemata/api.py b/packages/cmk-plugins/cmk/plugins/kube/schemata/api.py
index b2f8479db68..2667da4db44 100644
--- a/packages/cmk-plugins/cmk/plugins/kube/schemata/api.py
+++ b/packages/cmk-plugins/cmk/plugins/kube/schemata/api.py
@@ -649,7 +649,7 @@ class StatefulSetRollingUpdate(BaseModel):
 
     type_: Literal["StatefulSetRollingUpdate"] = Field("StatefulSetRollingUpdate")
     partition: int
-    max_unavailable: str | None = Field(None)
+    max_unavailable: str | int | None = Field(None)
 
 
 class Recreate(BaseModel):