kubectl explain --output flag is missing -o short flag

[brianpursley]

What happened:
kubectl explain has an --output flag, but unlike all other kubectl commands, there is no corresponding -o short flag:

What you expected to happen:
For consistency, kubectl explain should have a -o short flag like other commands that have an --output flag.

How to reproduce it (as minimally and precisely as possible):

~/go/src/k8s.io/kubernetes (master) $ kubectl explain pod -o plaintext-openapiv2
error: unknown shorthand flag: 'o' in -o
See 'kubectl explain --help' for usage.

~/go/src/k8s.io/kubernetes (master) $ kubectl explain pod --output plaintext-openapiv2
KIND:     Pod
VERSION:  v1

DESCRIPTION:
     Pod is a collection of containers that can run on a host. This resource is
     created by clients and scheduled onto hosts.

FIELDS:
   apiVersion	<string>
     APIVersion defines the versioned schema of this representation of an
     object. Servers should convert recognized schemas to the latest internal
     value, and may reject unrecognized values. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources

   kind	<string>
     Kind is a string value representing the REST resource this object
     represents. Servers may infer this from the endpoint the client submits
     requests to. Cannot be updated. In CamelCase. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds

   metadata	<Object>
     Standard object's metadata. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

   spec	<Object>
     Specification of the desired behavior of the pod. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

   status	<Object>
     Most recently observed status of the pod. This data may not be up to date.
     Populated by the system. Read-only. More info:
     https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

Anything else we need to know?:

Environment:

• Kubernetes client and server versions (use kubectl version):

Client Version: v1.32.0-alpha.0.1230+7478a30fdc6977
Kustomize Version: v5.4.2
Server Version: v1.27.3
WARNING: version difference between client (1.32) and server (1.27) exceeds the supported minor version skew of +/-1

• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release): Ubuntu 22.04.5 LTS

[brianpursley]

/good-first-issue

[k8s-ci-robot]

@brianpursley:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ardaguclu]

/triage accepted
/priority backlog

[ak20102763]

Hi @brianpursley / @ardaguclu , may I take this up