There are some changes in Kube 1.15 to how CRDs are handled. See
https://kubernetes.io/blog/2019/06/20/crd-structural-schema/ for more details. We should investigate how these changes impact our existing CRDs.

The resolution of this issue should be:

• either the necessary changes to our schemas and CRD support (e.g. crd-generator) and api, or
• an epic and tasks linked to it to do the actual work, if it turns out there's a lot of changes involved.

This will ensure our CRDs continue to work nicely in Kubernetes 1.15 and 1.16.