Currently schema validation prevents usage of affinity field with error like the following one:
Error: values don't meet the specifications of the schema(s) in the following chart(s):
timescaledb-single:
- affinity: Additional property nodeAffinity is not allowed
- affinity: Additional property podAntiAffinity is not allowed
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
What this PR does / why we need it
Currently schema validation prevents usage of
affinityfield with error like the following one:Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged)Special notes for your reviewer
Checklist