kubernetes-client/python

CRD version properties are inadvertently removed when serializing

Open

#2,436 创建于 2025年8月14日

在 GitHub 查看
 (3 评论) (0 反应) (1 负责人)Python (6,225 star) (3,323 fork)batch import
help wantedkind/bug

描述

Summary

I am loading a V1CustomResourceDefinition, making a small modification to it, then re-serializing it, and I am seeing numerous unintended mutations / removals made to the resulting output CRD

Similar defect as:

Details

Here are the sequence of diffs for my CRD:

@@ -17,111 +16,12 @@

   group: mycr.me.com
   names:
     kind: MyCR
-    listKind: MyCRList
     plural: mycrs
     singular: mycr

...

-  ... (Removed additionalPrinterColumns)
-  ... (Removed the entire version schema)
+  - name: v1beta1
+    schema: {}

贡献者指南

技术栈
pythonrest api
领域
backendapi
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Python kubernetes client basicsUnderstanding of CRD structureKnowledge of JSON serialization
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Start by examining the serialization logic for V1CustomResourceDefinition in the Python client. The issue is similar to #2435, so review the fix for that issue. Look at how version properties are handled during serialization, particularly the 'preserveUnknownFields' or schema handling. Check files in kubernetes/client/models/ and any custom serializers. Attempt to reproduce the bug using the provided CRD example and trace the serialization path.
CRD version properties are inadvertently removed when serializing · kubernetes-client/python#2436 | Good First Issue