Working example

[devdattakulkarni]

Working example

[devdattakulkarni]

@dailong If you add // +k8s:openapi-gen=true on your Type definition then you should be able to generate OpenAPI Spec for your Type. If there is any validation error then fix your Type definition and try again. The error that I have ran into typically is the name validation error. This means that in the type definition there is some problem with how names are defined in the type spec or the type status definition. The main issue for me has been when field name defined in the Go code and field name expected as json have been different. kube-openapi name validation rules expect the field name in Go code and field name in json to be exactly same with just the first letter in different case (Go code requires CamelCase, json requires camelCase). So keep an eye out for such an issue in your type definition.

Another issue that I have ran into is that kube-openapi doesn't seem to understand ObjectMeta and ListMeta types.

I have put together a small utility to make it easy to generate OpenAPI Spec for custom Types. You can find it here:
https://github.com/cloud-ark/kubeplus/tree/master/openapi-spec-generator

The driver script works on a copy of your types.go. It comments out lines containing ObjectMeta and ListMeta and then runs this modified types.go through kube-openapi.
README gives the steps that you can follow to generate OpenAPI Spec for your type. Hopefully it helps.

[dailong]

I have this problem too. How did you solve it?

[dailong]

I got it. thanks

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.