fix(k8s): alias apimachinery.pkg.apis.meta.v1 imports in 1.14 - 1.31

[Peefy]

Summary

Up to and including k8s 1.31, the auto-generated KCL schema packages imported apimachinery.pkg.apis.meta.v1 without an alias:

import apimachinery.pkg.apis.meta.v1

schema X:
    foo?: v1.Condition

This breaks whenever the parent package is imported via as <alias> (e.g. import k8s.api.networking.v1 as netv1), because the relative-import resolver does not fall back into the parent-package namespace. Symptom:

error[E2G22]: attribute 'Condition' not found in 'module 'apimachinery.pkg.apis.meta.v1''

This is the same class of bug that surfaced in discussion #2127 (the user hit it via kcl_lib on Windows with k8s/1.28), and it also blocks konfig's nginx-example which pins k8s = "1.31.2".

Fix

Promote every import apimachinery.pkg.apis.meta.v1 to import apimachinery.pkg.apis.meta.v1 as metav1, and rewrite in-file v1.<Type> references to metav1.<Type>. This matches the pattern already shipped in k8s 1.32+, so nothing breaks forward.

Files touched:

version	files
1.14	208
1.15	210
1.16	221
1.17	227
1.18	191
1.19	197
1.20	204
1.21	212
1.22	168
1.23	162
1.24	161
1.25	141
1.26	153
1.27	157
1.28	158
1.29	169
1.30	184
1.31	186

Total: 3308 files, 10174 insertions(+), 10174 deletions(-) (one-line mechanical rewrite).

Verification

Tested locally with a fresh kcl mod init + k8s = { path = "k8s/1.28" } dep:

import k8s.api.networking.v1 as netv1

result = netv1.NetworkPolicy {
    metadata.name = "test"
    spec = {
        podSelector = { matchLabels = { app = "demo" } }
        policyTypes = ["Ingress"]
        ingress = [{
            from = [{ podSelector = { matchLabels = { app = "frontend" } } }]
            ports = [{ protocol = "TCP", port = 80 }]
        }]
    }
}

Compiles clean. Before the fix this fails with attribute 'Condition' not found in 'module 'apimachinery.pkg.apis.meta.v1''.

Note for the schema-generator side

The right long-term fix is in the upstream KCL schema generator — it should emit as metav1 (and any other v1.X aliases) by default. Until then, this PR keeps the published k8s/1.14-1.31 modules usable.

Related

• discussion #2127 (vendored k8s/1.28 hits the same bug from kcl_lib)
• konfig nginx-example (kcl.mod pins k8s = "1.31.2")