Sometimes I get an error about how the manifest is malformed. When that happens it's super hard to troubleshoot. If the kubernetes plugin would print the manifests contents, that would help.
If we run the following command before apply, we can get the rendered manifest printed out when --debug is set.
kubectl apply -f FILE --dry-run=client -o yaml
I checked and if we just specify -o yaml, it won't print the manifest until after its run, so when there's a problem with it, you can't see the file contents. So doing two commands, first dry-run, then apply, in debug mode would give you enough info to figure out what went wrong hopefully.
Sometimes I get an error about how the manifest is malformed. When that happens it's super hard to troubleshoot. If the kubernetes plugin would print the manifests contents, that would help.
If we run the following command before apply, we can get the rendered manifest printed out when --debug is set.
I checked and if we just specify -o yaml, it won't print the manifest until after its run, so when there's a problem with it, you can't see the file contents. So doing two commands, first dry-run, then apply, in debug mode would give you enough info to figure out what went wrong hopefully.