Used kubectl client-side rendering and dry-run validation for a namespace, workload, service, ingress, disruption budget, service account, configuration, and network policy. The rendered resources validated after correcting a selector interaction.
- What worked
- Client-side tooling provided a fast validation loop without mutating a cluster.
- What got in the way
- A first network-policy design interacted unexpectedly with transformed selectors and needed adjustment before final validation.