Feature Request: Enable field-level type validation in nomos vet #2022
Description
Checklist
- I did not find a related open enhancement request.
- I understand that enhancement requests filed in the GitHub repository are by default low priority.
- If this request is time-sensitive, I have submitted a corresponding issue with GCP support.
Describe the feature
Description: Currently, nomos vet parses objects into Unstructured objects and does not convert them into typed objects. As a result, it does not perform field-level type validation. Users can pass validation with invalid YAML—such as providing a boolean true instead of a string "true" in a ConfigMap—only to encounter sync failures (e.g., KNV2009) when the reconciler attempts to apply the resource.
Feature request: We request that nomos vet be enhanced to support field-level type validation. The tool should check resource definitions against their schema (server-side or client-side) to catch type mismatches, such as boolean values in string-only fields, before they reach the cluster.
Alternatives considered:
- Manual Workarounds: Ensuring all values are explicitly quoted (e.g., "true").
- Server-side Dry Run: Running nomos hydrate --flat --clusters=CLUSTER | kubectl apply --dry-run=server -f- to validate rendering and types.
- Third-party Tools: Using kubeconform for client-side validation, though this does not handle rendering or server-side checks.
Importance
No response