Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment API version apps/v1beta2 is being changed to extensions/v1beta1 on creation #58895

Closed
sean-krail opened this issue Jan 27, 2018 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.

Comments

@sean-krail
Copy link

sean-krail commented Jan 27, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:

When I create an example Deployment found at kubernetes/website with api version apps/v1beta2, the api version I see when I perform kubectl get deploy nginx-deployment -o yaml is extensions/v1beta1.

What you expected to happen:

I expect the api version to be apps/v1beta2.

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

  • Use client version v1.9.1 and server version v1.8.4.
  • Create the example Nginx Deployment file:
    kubectl create -f https://raw.githubusercontent.com/kubernetes/website/snapshot-final-v1.8/docs/tasks/run-application/deployment.yaml
  • Check that the api version is apps/v1beta2 (which it isn't):
    kubectl get deploy nginx-deployment -o yaml | grep apiVersion

Anything else we need to know?:

Not that I can think of.

Environment:

  • Kubernetes version (use kubectl version):

    Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1", GitCommit:"3a1c9449a956b6026f075fa3134ff92f7d55f812", GitTreeState:"clean", BuildDate:"2018-01-04T11:52:23Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:17:43Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration:

    AWS, deployed via kops v1.8.0 (git-5099bc5)

  • OS (e.g. from /etc/os-release): ~

  • Kernel (e.g. uname -a): ~

  • Install tools:

    kops v1.8.0 (git-5099bc5)

  • Others: ~

@k8s-ci-robot
Copy link
Contributor

@sean-krail: There are no sig labels on this issue. Please add a sig label.

A sig label can be added by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

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.

@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. kind/bug Categorizes issue or PR as related to a bug. labels Jan 27, 2018
@liggitt
Copy link
Member

liggitt commented Jan 27, 2018

kubectl get deployment without qualification gets the first version of deployments the server indicates it is capable of returning.

The deployment you created can be retrieved in any of the supported versions. To get a specific group or version, fully qualify your get request:

kubectl get deployment.apps …
kubectl get deployment.v1beta2.apps …

/close

@sean-krail
Copy link
Author

That's confusing. I would think that it would return the version that I uploaded or the latest version of deployments the server is capable of returning.

Anyways, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants