Reducing yaml file for VitessCluster Kind

Do we have any option for maintaining clearness with VitessCluster Kind yaml file?
So what we have noticed about it:

• repeatable vttablet extra flags for each keyspace
• repeatable vttablet affinity definition for each keyspace
• repeatable vttablet volumes, volumeMounts, extraEnv, mysqld configOverrides, sidecarContainers

All of these makes a huge yaml file when you have a lot of keyspaces defined.
Is there any options for definition of common configs etc. to be reused/included for each keyspaces and only some specific configs to be added under keyspaces?

With around 10 keyspaces we have almost 2k+ lines of cluster definition (it could be reduced without those repetitive stuff there)
Also noticed some flags don't have same key name, but hold the same value for example:
vtgate vault flags

• mysql_auth_vault_addr:
• mysql_auth_vault_path:
• mysql_auth_vault_ttl:

vttablet vault flags

• db-credentials-vault-ttl:
• db-credentials-vault-addr:
• db-credentials-vault-path:

Start by reviewing the VitessCluster Kind YAML and catalog the repeated vttablet flags, affinity, volumes, mounts, environment, mysqld overrides, and sidecar definitions across keyspaces. Compare the vtgate and vttablet Vault flag names and clarify the desired reuse or inclusion mechanism; the issue does not define an implementation or acceptance criteria.