[Question] Why is uint32 mapped to {"integer", "int64", 0.}

[manusa]

Description

uint32 is currently mapped to OpenAPI numeric integertype which seems OK, but with a format of int64.
Is there any reason for this? or is it a typo?

The mapping is located here:

kube-openapi/pkg/common/common.go

Line 187 in 67ed584

"uint32": {"integer", "int64", 0.},

This is problematic because at the moment, for example, fields representing server ports are typed as int64 which map them to misleading types such as Long in Java.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[manusa]

/remove-lifecycle stale

[Jefftree]

so this existed pretty much since the inception of the repo, my understanding is that a max size uint32 would not fit in an int32 because of the extra bit required and we go to the next size of 64. You could use a signed int32?