API changes to better respect k8s conventions

[mandre]

What would you like to see implemented?

Recent changes to kube-api-linter highlighted problems in our API:

• optional fields are supposed to be pointers
• required fields that have a valid zero value should be pointers

We had to disable these checks as they would introduce backward incompatible changes in the API. There may be other issues not listed here. We should thoroughly review the ORC prior to the next major bump.

Kubernetes API conventions for reference: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#optional-vs-required

Additional information

No response

Link to reference documentation

No response