Missing subcommand disable flags parsing

[zoriya]

When a subcommand is required but not provided, it outputs an error (expected). Example:

$ kubectl create svc
Create a service using a specified subcommand.
Aliases:
service, svc
Available Commands:
  clusterip      Create a ClusterIP service
  externalname   Create an ExternalName service
  loadbalancer   Create a LoadBalancer service
  nodeport       Create a NodePort service
Usage:
  kubectl create service [flags] [options]
Use "kubectl create service <command> --help" for more information about a given command.
Use "kubectl options" for a list of global command-line options (applies to all commands).

But when we have (valid) flags already specified we get a unknown flag error:

$ kubectl create -o yaml svc
error: unknown shorthand flag: 'o' in -o
See 'kubectl create service --help' for usage.

I would expect the -o yaml flag (specified by the create subcommand) to be silently accepted and get back the error/help output we get with kubectl create svc.

[zoriya]

I don't know if i should create a new issue for this but note that specifying a flag disable autocompletion of sub commands.

Example:

$ kubectl create <Tab>
 -- completions --
clusterrolebinding   -- Create a cluster role binding for a particular cluster role
clusterrole          -- Create a cluster role
configmap            -- Create a config map from a local file, directory or literal value
cronjob              -- Create a cron job with the specified name
deployment           -- Create a deployment with the specified name
ingress              -- Create an ingress with the specified name
job                  -- Create a job with the specified name
namespace            -- Create a namespace with the specified name
poddisruptionbudget  -- Create a pod disruption budget with the specified name
priorityclass        -- Create a priority class with the specified name
quota                -- Create a quota with the specified name
rolebinding          -- Create a role binding for a particular role or cluster role
role                 -- Create a role with single rule
secret               -- Create a secret using a specified subcommand
serviceaccount       -- Create a service account with the specified name
service              -- Create a service using a specified subcommand
token                -- Request a service account token

$ kubectl create -o yaml <Tab>
 -- filename --
README.md     taskfile.yaml

Once again, i would expect the -o yaml flag to be accepted and not affect completion results.