This message was deleted.
# fleet
a
This message was deleted.
g
I could, but that's an antipattern for most. That's what I've done in the past and it's just about the only code I have to deploy with nearly zero linting/validation prior to committing to main
a
Interesting but I haven’t seen any tools as of yet, like dry run I think you can call this via kubectl
—dry-run=client
g
Yeah, it's disappointing. We have kubectl in our pipeline for various things, but there are so many issues which are Fleet specific. I do a lot with helm+kustomize. Also there are some Fleet specific things. When there are issues, they only show themselves with Fleet, not with Kustomize, kubectl, etc
a
But validating helm charts and whole kustomize is a different story
g
For sure. Ideally we would be able to do some sort of dry run with fleet, consuming the manifests, reporting any errors.
however, thanks for responding!
👍 1