Custom JSON marshaling causes schema validation generation to be skipped

[christarazi]

I have a CRD type as follows:

type A struct {
  metav1.TypeMeta
  metav1.TypeMeta

  Spec   Spec
  Status Status
}

The Spec field implements custom JSON marshaling. This causes the validation schema generation for Spec to be skipped, and replaced with type: Any. This is due to #427.

I expect to control this with a marker, or a similar knob. In this case, an opt-out marker makes sense if #427 implements sane default behavior.

[alvaroaleman]

We've reverted #427 in #505 as type: Any is not valid.
/close

Feel free to re-open if you think the revert doesn't address the issue.

[k8s-ci-robot]

@alvaroaleman: Closing this issue.

In response to this:

We've reverted #427 in #505 as type: Any is not valid.
/close

Feel free to re-open if you think the revert doesn't address the issue.

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.