From: David Karr <davidmichaelkarr@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: "kubectl exec" in Cygwin gets "Upgrade request required", but not in cmd shell
Date: Sat, 13 Jun 2020 11:53:48 -0700 [thread overview]
Message-ID: <CAA5t8VqpU2KiQ_Kk5czjLzeCDzf21Gb2iBLu25xB43ZhpfmaPQ@mail.gmail.com> (raw)
I've been using kubectl in Cygwin on Windows 10 for quite a while, to
communicate to our in-house k8s clusters. I often use "kubectl exec" to
open a shell in a container or directly execute a shell command. This has
worked perfectly fine for a long time.
A couple of days ago, I discovered that all of these attempts were failing
with "Upgrade request required". I hadn't upgraded kubectl or Cygwin in
quite a while. I doubt our clusters had a k8s upgrade, but it's entirely
possible.
A colleague of mine has a very similar desktop configuration (Windows 10,
Cygwin), and he's not seeing this symptom.
I noticed that when I ran "kubectl exec" with max verbosity, it shows the
resulting "curl" command that it runs. I tried that resulting command, and
it results in the same response. I then tried updating my Cygwin tools and
retesting, no change.
I then took the entire resulting "kubectl exec" command line and ran it in
a "cmd" shell. No problem at all. No error.
I know I haven't provided much useful information yet. I wanted to get an
initial response before I started providing those diagnostics. Is there a
clear issue here that I'm not aware of?
next reply other threads:[~2020-06-13 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 18:53 David Karr [this message]
2020-06-14 5:30 ` Marco Atzeri
2020-06-14 6:12 ` David Karr
2020-06-14 9:25 ` Marco Atzeri
2020-06-14 15:38 ` David Karr
2020-06-14 17:03 ` Marco Atzeri
2020-06-14 17:19 ` Brian Inglis
2020-06-14 18:16 ` David Karr
2020-06-14 19:08 ` Brian Inglis
2020-06-14 19:32 ` David Karr
2020-06-15 16:10 ` David Karr
2020-06-17 16:39 ` David Karr
2020-06-18 0:27 ` Brian Inglis
2020-06-18 17:53 ` David Karr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA5t8VqpU2KiQ_Kk5czjLzeCDzf21Gb2iBLu25xB43ZhpfmaPQ@mail.gmail.com \
--to=davidmichaelkarr@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).