The generated CRD yaml can't pass `kubeconform -ignore-missing-schemas -strict`

It fails with

CustomResourceDefinition clickhouseinstallations.clickhouse.altinity.com failed validation: error unmarshalling resource: error converting YAML to JSON: yaml: unmarshal errors:
  line 311: key "description" already set in map
  line 384: key "type" already set in map
  line 394: key "description" already set in map
  line 397: key "description" already set in map
  line 400: key "description" already set in map
  line 410: key "description" already set in map
  line 413: key "description" already set in map
  line 416: key "description" already set in map
  line 419: key "description" already set in map
  line 429: key "description" already set in map
  line 528: key "description" already set in map
  line 528: key "description" already set in map
  ...

Probably because TypeStringBool has description and type fields, but we try to override them later, which is not allowed by kubeconform. Can we somehow fix it?

Start by locating the CRD-generation path and the TypeStringBool definition referenced in the issue, then inspect how its description and type fields are overridden. Reproduce the failure with kubeconform -ignore-missing-schemas -strict against the generated CRD. Done means the generated CRD passes strict validation without duplicate YAML keys.