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

krew kubectl install ingress-nginx not working #12452

Open
kundan2707 opened this issue Dec 9, 2024 · 4 comments
Open

krew kubectl install ingress-nginx not working #12452

kundan2707 opened this issue Dec 9, 2024 · 4 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@kundan2707
Copy link
Contributor

What happened:
ingress-nginx plugin got kubectl not working

What you expected to happen:
It should work

NGINX Ingress controller version (exec into the pod and run /nginx-ingress-controller --version):

Kubernetes version (use kubectl version):

  • kubectl version
    Client Version: v1.31.0
    Kustomize Version: v5.4.2
    Server Version: v1.31.3

Environment:
Baremetal Ubuntu

  • How was the ingress-nginx-controller installed:
    Failed in installation

  • Current State of the controller:

NA

  • Current state of ingress object, if applicable:

NA

  • Others:

How to reproduce this issue:
install krew
kubectl krew install ingress-nginx

Anything else we need to know:

@kundan2707 kundan2707 added the kind/bug Categorizes issue or PR as related to a bug. label Dec 9, 2024
@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Dec 9, 2024
@kundan2707
Copy link
Contributor Author

kubectl krew install ingress-nginx
+ kubectl krew install ingress-nginx
Updated the local copy of plugin index.
Installing plugin: ingress-nginx
W1209 10:25:24.005490  818702 install.go:164] failed to install plugin "ingress-nginx": install failed: failed to unpack into staging dir: failed to unpack the plugin archive: failed to obtain plugin archive: failed to download "https://github.com/kubernetes/ingress-nginx/releases/download/controller-0.31.0/kubectl-ingress_nginx-linux-amd64.tar.gz", status code 404
failed to install some plugins: [ingress-nginx]: install failed: failed to unpack into staging dir: failed to unpack the plugin archive: failed to obtain plugin archive: failed to download "https://github.com/kubernetes/ingress-nginx/releases/download/controller-0.31.0/kubectl-ingress_nginx-linux-amd64.tar.gz", status code 404

@kundan2707
Copy link
Contributor Author

kubectl krew info ingress-nginx
+ kubectl krew info ingress-nginx
NAME: ingress-nginx
INDEX: default
URI: https://github.com/kubernetes/ingress-nginx/releases/download/controller-0.31.0/kubectl-ingress_nginx-linux-amd64.tar.gz
SHA256: f9555f2a3f60bba86fe3d567f10bacdd6a84cde15ac98c377ee68fa5c44957ff
VERSION: v0.31.0
HOMEPAGE: https://kubernetes.github.io/ingress-nginx/kubectl-plugin/
DESCRIPTION: 
The official kubectl plugin for ingress-nginx.

@kundan2707
Copy link
Contributor Author

It is still trying to download 0.31.0 controller which is obsolete.

@strongjz
Copy link
Member

It looks like the go releaser was silently failing; it was updated, and we are releasing 1.12 soon. We will then know if the GHA was fixed and can look into what it would take to update others.

/priority backlog
/triage accepted
/assign @strongjz

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 12, 2024
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. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

No branches or pull requests

3 participants