Package: kubernetes-client Version: 1.7.7+dfsg-2 Severity: important Dear Maintainer,
The current version of kubernetes-client in Debian seems to have a bug in option handling. Any server or user flags specified on the command line or in ~/.kube/config are ignored. Instead, kubectl always tries to connect to http://localhost:8080, which may work for some use cases, but is generally wrong. Example command line: $ kubectl --server https://remote.host get nodes Expected result: kubectl get nodes NAME STATUS AGE worker1 Ready 1d Actual result: The connection to the server localhost:8080 was refused - did you specify the right host or port? For some odd reason, kubectl config works fine - managing ~/.kube/config, switching contexts etc. is no problem at all. I encountered the same problem on two different machines. kubectl was still fine until a few days ago. Thanks. -- System Information: Debian Release: buster/sid APT prefers stable APT policy: (999, 'stable'), (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kubernetes-client depends on: ii libc6 2.24-11+deb9u1 kubernetes-client recommends no packages. kubernetes-client suggests no packages. -- no debconf information
