Closed jpbetz closed 4 years ago
BackendConfig CRDs are non-structural because they do not have pruning enabled (note in the CRD thatpreserveUnknownFields: true). See https://v1-17.docs.kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#publish-validation-schema-in-openapi-v2.
preserveUnknownFields: true
How to reproduce:
<apiserver-url>/openapi/v2
Pruning can be manually enabled by setting preserveUnknownFields: false in the BackendConfig CRD. Once enabled, /openapi/v2 returns the full schema.
preserveUnknownFields: false
/openapi/v2
I don't see any reason why pruning needs to be disabled for BackendConfig. It might be worth upgrading to the CRD v1 API at the same time?
@skmatti
/assign @skmatti
BackendConfig CRDs are non-structural because they do not have pruning enabled (note in the CRD that
preserveUnknownFields: true
). See https://v1-17.docs.kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#publish-validation-schema-in-openapi-v2.How to reproduce:
<apiserver-url>/openapi/v2
Pruning can be manually enabled by setting
preserveUnknownFields: false
in the BackendConfig CRD. Once enabled,/openapi/v2
returns the full schema.I don't see any reason why pruning needs to be disabled for BackendConfig. It might be worth upgrading to the CRD v1 API at the same time?