kubectl get/describe defaults to returning the GA API version for a K8s object.

[JoshuaFox]

kubectl get/describe defaults to returning the GA API version for a K8s object.

It seems to be strange -- we expect the kubectl command to give a true answer. In many case, the false answer actually has implications about what is and is not supported in the API.

As an example, you set up a HorizontalPodAutoscaler in v2beta2. You chose this rather than v1 specifically for the new API it gives you, custom metrics. Yet kubectl get/describe tells you that it is v1!

But regardless, is this fact documented? If so, where? If not, please document it.

[k8s-ci-robot]

@JoshuaFox: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[sftim]

The place that should explain this is https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning

However, some of the details are instead in https://kubernetes.io/docs/reference/using-api/#api-versioning and https://kubernetes.io/docs/reference/using-api/deprecation-policy/ (sic)

My proposed fix:

• update https://kubernetes.io/docs/reference/using-api/#api-versioning to clarify whether and why Kubernetes prefers stable API versions over newer, not yet stabilized APIs.
• clearly signpost readers to read about round-tripping (rule CSS: Styles are huge, generally #2 from https://kubernetes.io/docs/reference/using-api/deprecation-policy/) or repeat that detail within https://kubernetes.io/docs/concepts/overview/kubernetes-api/
• update https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-groups-and-versioning to link to the updated reference pages that are now more helpful because of these revisions.

/language en
/wg api-expression

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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/test-infra repository.