int-or-string parameters are typed out with mismatched "type" property

[zlepper]

int-or-string parameters are typed out with mismatched "type" property

[Arnavion]

However right now they are typed as:

Yes, because that's what Kubernetes' own spec has always done:

https://raw.githubusercontent.com/kubernetes/kubernetes/v1.29.1/api/openapi-spec/swagger.json

    "io.k8s.apimachinery.pkg.util.intstr.IntOrString": {
      "description": "IntOrString is a type that can hold an int32 or a string.  When used in JSON or YAML marshalling and unmarshalling, it produces or consumes the inner type.  This allows you to have, for example, a JSON field that can accept a name or number.",
      "format": "int-or-string",
      "type": "string"
    },

... so I'm surprised it wants a different thing for user-provided specs.

[zlepper]

I agree, it's kinda f'ed up.. however it's probably another lovely case of Kubernetes not using crd's to represent its own stuff, and thus the behave differently :/