Commit 4b9d2da
fix(core): normalize apiVersion during deserialization for backward compatibility
When a YAML file uses an old apiVersion (e.g., v1beta2) and no exact
match exists in the deserializer mapping, the LatestApiVersionResourceTypeResolver
resolves the correct class. However, the deserialized resource retained
the old apiVersion from the YAML, causing controller matching to fail
since controllers now only support v1.
This fix normalizes the apiVersion field in the JSON node before
deserialization when the type was resolved by a fallback resolver,
ensuring the resource carries the canonical version of the resolved class.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>1 parent c068fc9 commit 4b9d2da
1 file changed
Lines changed: 12 additions & 1 deletion
Lines changed: 12 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
| 13 | + | |
13 | 14 | | |
14 | 15 | | |
15 | 16 | | |
| |||
53 | 54 | | |
54 | 55 | | |
55 | 56 | | |
| 57 | + | |
56 | 58 | | |
57 | 59 | | |
58 | 60 | | |
| |||
79 | 81 | | |
80 | 82 | | |
81 | 83 | | |
| 84 | + | |
82 | 85 | | |
83 | 86 | | |
84 | 87 | | |
| |||
97 | 100 | | |
98 | 101 | | |
99 | 102 | | |
| 103 | + | |
100 | 104 | | |
101 | | - | |
| 105 | + | |
102 | 106 | | |
103 | 107 | | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
104 | 115 | | |
105 | 116 | | |
106 | 117 | | |
| |||
0 commit comments