Have you tried --validate, which reads the swagger?

diff and dry-run are already in cli-roadmap.md.

See also #5889 and #6284.

Another case where more info is desired on failure is update failure. Somewhere we discussed returning the whole object on conflict, for instance. A related discussion is #9569 (comment)
cc @smarterclayton @lavalamp

Related: #8668

I would prefer to have this behavior by default for our error object if we
can - it's a big performance win and reduces client annoyance.

On Jul 1, 2015, at 5:30 PM, Brian Grant notifications@github.com wrote:

Another case where more info is desired on failure is update failure.
Somewhere we discussed returning the whole object on conflict, for
instance. A related discussion is #9569 (comment)
#9569 (comment)
cc @smarterclayton https://github.com/smarterclayton @lavalamp
https://github.com/lavalamp

—
Reply to this email directly or view it on GitHub
#6132 (comment)
.

@thockin There are no sig labels on this issue. Please add a sig label by:
(1) mentioning a sig: @kubernetes/sig-<team-name>-misc
(2) specifying the label manually: /sig <label>

Note: method (1) will trigger a notification to the team. You can find the team list here.

@kubernetes/sig-cli-misc

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

/remove-lifecycle stale
/lifecycle frozen

Hi @thockin, @smarterclayton, @bgrant0607
This issue has been open for a while, so I'm just checking to see if it is still an issue or not in the latest version.

It looks like there currently are some useful error messages given when there are problems with the json. Do you think these are sufficient or is something more detailed needed?

Here is what I tried, using kubectl v1.18.0:

Test 1: Invalid json (removed " before metadata)

kubectl create -f - << EOF
{
    "kind": "Pod",
    "apiVersion": "v1",
    metadata": {
        "name": "nginx"
    },
    "spec": {
        "containers": [
            {
                "name": "nginx",
                "image": "nginx"
            }
        ],
        "restartPolicy": "Never"
    }
}
EOF

error: error parsing STDIN: json: line 3: invalid character 'm' looking for beginning of object key string

Test 2: Json is valid but does not conform (changed spec to xspec)

kubectl create -f - << EOF
{
    "kind": "Pod",
    "apiVersion": "v1",
    "metadata": {
        "name": "nginx"
    },
    "xspec": {
        "containers": [
            {
                "name": "nginx",
                "image": "nginx"
            }
        ],
        "restartPolicy": "Never"
    }
}
EOF

error: error validating "STDIN": error validating data: ValidationError(Pod): unknown field "xspec" in io.k8s.api.core.v1.Pod; if you choose to ignore these errors, turn validation off with --validate=false

Thanks. I think we can close this.
/close

@bgrant0607: Closing this issue.