3 ms·
Working with helm values schemas is a pain (I do it a lot), but I would argue that it's actually far more effective than this method of using CEL at ensuring an
by glitchcrab 2y ago
Working with helm values schemas is a pain (I do it a lot), but I would argue that it's actually far more effective than this method of using CEL at ensuring an entire values file is correct (both syntactically and also accurate).
Using CEL in this way is useful if you want to ensure _some_ of the values are enforced, but it serves a somewhat different purpose.
- idsulik_dev 2y agoTrue about completeness, but I've found that teams often struggle with JSON Schema's verbosity and complexity when writing validation rules. CEL lets you express the same constraints in a more natural way - compare "!has(values.persistence) || has(values.storageClass)" vs nested if/then JSON Schema structure. The tradeoff is worth it when readability and maintainability are priorities.