Hi Nicolas, Thanks for your report. I will look into this one. There was a reason I was reluctant to "upgrade" golang
On Tue, 12 Apr 2022, 11:39 Nicolas Noirbent, <nico...@noirbent.fr> wrote: > Package: kubernetes-client > Version: 1.20.5+really1.20.2-1.1 > Severity: normal > > Dear Maintainer, > > Since the upgrade to version 1.20.5+really1.20.2-1.1, using "kubernetes > config use-context" to > switch context systematically triggers SIGSEGV: > > % kubectl config use-context dev-go-cell-001 > unexpected fault address 0x0 > fatal error: fault > [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x46421f] > […] > > This also obviously affects kubectx and kubens (which uses kubectl config > use-context); however it > does not preclude from manually setting a context / namespace when running > regular kubectl > commands, e.g.: > > % kubectl --context dev-go-cell-001 --namespace hello-world get pods > NAME READY STATUS RESTARTS AGE > […] > > Downgrading to 1.20.5+really1.20.2-1 fixes the issue, so I suspect this > has something to do with > the switch to golang 1.18 done to fix # > https://bugs.debian.org/cgi-bin/bugreport.cgi?1000980 > > Regards, > > -- System Information: > Debian Release: bookworm/sid > APT prefers stable-security > APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) > Kernel taint flags: TAINT_WARN > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > -- no debconf information >
