Reject unknown fields in the CR about flink-on-k8s-operator HOT 4 OPEN

Do you mean pruning function?
If so, since version 1.15 it seems to be supported by k8s apiserver.

note: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#pruning-versus-preserving-unknown-fields

I tested this feature in 1.15, but there were another problem. controller-tools included in kubebuilder is not able to create a "structural schema" intact. To use the pruning feature, the openapi validation schema must be defined as "structural schema". There are two issues with structural schema that are problematic.

kubernetes-sigs/controller-tools#304 (resolved recently)
kubernetes-sigs/controller-tools#279

from flink-on-k8s-operator.

controller-tools 0.2.4 included in kubebuilder v2.2.0 supports the generation of CRD V1 and structural schema, which allows you to use preserveUnknownFields. If you are using k8s 1.15 this issue seems to be resolved.

I have tested generating CRD with controller-tools 0.2.4, deploying CRD to k8s 1.15 cluster and deploying CR with unknown field, and api-server-validation works well.

• note:
  https://github.com/kubernetes-sigs/controller-tools/releases/tag/v0.2.3
  https://github.com/kubernetes-sigs/kubebuilder/blob/v2.2.0/scripts/setup.sh#L28

from flink-on-k8s-operator.

This doesn't seem to be supported by Kubebuilder kubernetes-sigs/kubebuilder#1174. Still not aware of how to solve it.

from flink-on-k8s-operator.

Thanks, will check!

from flink-on-k8s-operator.