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
Do we have any option for maintaining clearness with VitessCluster Kind yaml file? So what we have noticed about it:
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
vttablet vault flags