Skip to content

describe resource fail for kubectl v1.32.2 #1723

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

Open
TigerWj opened this issue Feb 24, 2025 · 2 comments
Open

describe resource fail for kubectl v1.32.2 #1723

TigerWj opened this issue Feb 24, 2025 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@TigerWj
Copy link

TigerWj commented Feb 24, 2025

What happened:
fail to describe deployment when using the latest kubectl.
commond:
./kubectl-1.32.2 describe deployment --kubeconfig ./kubeconfig
error:
Error from server (NotAcceptable): object *v1.Deployment does not implement the protobuf marshalling interface and cannot be encoded to a protobuf message

What you expected to happen:

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

Anything else we need to know?:

Environment:

  • Kubernetes client and server versions (use kubectl version): v1.32.2
  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release): linux amd64
@TigerWj TigerWj added the kind/bug Categorizes issue or PR as related to a bug. label Feb 24, 2025
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 24, 2025
@TigerWj TigerWj changed the title decsribe fail for kubectlv 1.32.2 decsribe fail for kubectl v1.32.2 Feb 24, 2025
@TigerWj TigerWj changed the title decsribe fail for kubectl v1.32.2 describe resource fail for kubectl v1.32.2 Feb 24, 2025
@mpuckett159
Copy link
Contributor

/triage accepted
This is likely because the deployment name is missing, but the error should say that not a protobuf error.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 26, 2025
@omerap12
Copy link
Member

omerap12 commented Mar 7, 2025

Can you elaborate more on the steps to reproduce the issue?
I tried running the following commands but didn't encounter any errors:

 ~/ k version
Client Version: v1.32.2
Kustomize Version: v5.5.0
Server Version: v1.32.2
 ~/ k describe deployment --kubeconfig $HOME/.kube/config 
Name:                   nginx-deployment
Namespace:              default
CreationTimestamp:      Fri, 07 Mar 2025 22:56:35 +0200
Labels:                 app=nginx
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               app=nginx
Replicas:               3 desired | 3 updated | 3 total | 0 available | 3 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:  app=nginx
  Containers:
   nginx:
    Image:         nginx:1.14.2
    Port:          80/TCP
    Host Port:     0/TCP
    Environment:   <none>
    Mounts:        <none>
  Volumes:         <none>
  Node-Selectors:  <none>
  Tolerations:     <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      False   MinimumReplicasUnavailable
  Progressing    True    ReplicaSetUpdated
OldReplicaSets:  <none>
NewReplicaSet:   nginx-deployment-647677fc66 (3/3 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  9s    deployment-controller  Scaled up replica set nginx-deployment-647677fc66 from 0 to 3

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. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants