X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org EB3AE395B08C
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1592115140;
	bh=zBl8FCAreyrrLW23R+B+oAuZSxeT0N4tVO2gQnsfwRQ=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=T28rSAunkK/VBexT4V0fjwTS9WA8vp5Mj+VNkEEMMxAggeJUiHGJ0AZyxghG/8OfT
	bIkufoON8E5n7m7ro0SinZx/TQ3O/OCNbEwPIqRFEdliCV0jlzT7ZtrsKup5cID3fd
	Bzr+k2gZSC9Xkra7qLDgLw8ESb3Uc2sS5yhmQ07s=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 0EA28386F81C
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:cc;
	bh=uIzwhmvhmGQ/+rIWzlSWvetN7xeJnJKM7570upJxy0Q=;
	b=Ofugsa7KbRbhcZI4ddZn/0PfxAdkFK4RweR8Cov7ei5IXI6iO+EwL6BqEJ7Bkb17OK
	8w9FugD0F2rSTTkUpyq7+IhfZvA1QLhx5rRtZ6qx0V7mBKckmuonLQysFp1yP+45ER5I
	31U6jQLCUQHoNykiX33puVyyaMpWmdNjLUMlzN8FKzgqSAFhfPTs+vNHWTmF392HLoYB
	F5q1tvLsdyuhVP0x2JdxzFdk+yz9KLA8mkAJ+IVUzaRibyjuPqZuDHDT8NzDzMMdM7oX
	JxX7thzaRq2iFBri2sRDPGBxlqLDjGwgaVaHu9PEZOwHNjtCqTXCUQLQl8AeEzCu72uV
	GsZQ==
X-Gm-Message-State:	AOAM5317MFH0rpWzUG37Fi/WO2oaVg9CmFGsqEA0auS85AjVGxTOZnyi
	cxu0oFMLKWh9Xvc1yYWIEeGMu2MpwP/zy9pRttA=
X-Google-Smtp-Source:	ABdhPJwNixcVgvYz+OMUMD5ZiflMrZ3toigcop+Y4LBhlnD3RGzEpGhBffQNvKv7531RhcK9ihTXHVZVkhOXdD871nI=
X-Received:	by 2002:a9d:6013:: with SMTP id h19mr17727398otj.50.1592115137367;
	Sat, 13 Jun 2020 23:12:17 -0700 (PDT)
MIME-Version:	1.0
References:	<CAA5t8VqpU2KiQ_Kk5czjLzeCDzf21Gb2iBLu25xB43ZhpfmaPQ AT mail DOT gmail DOT com>
	<b68e371b-4e3d-3ab3-9a0e-2461697d814d AT gmail DOT com>
In-Reply-To:	<b68e371b-4e3d-3ab3-9a0e-2461697d814d@gmail.com>
Date:	Sat, 13 Jun 2020 23:12:06 -0700
Message-ID:	<CAA5t8Vpym95FDhvanJSNd910kWssJqK46ZzmF2jckQbY_7YxOw@mail.gmail.com>
Subject:	Re: "kubectl exec" in Cygwin gets "Upgrade request required", but not
	in cmd shell
To:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
X-Spam-Status:	No, score=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-Content-Filtered-By:	Mailman/MimeDel 2.1.29
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	David Karr via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	David Karr <davidmichaelkarr AT gmail DOT com>
Cc:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On Sat, Jun 13, 2020 at 10:31 PM Marco Atzeri via Cygwin wrote:

> On 13.06.2020 20:53, David Karr via Cygwin wrote:
> > 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?
> > --
>
> from where is kubectl coming from ?
>
> In cygwin I found only a kubectl.py in the ansible package
>

It's from here:
https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl-on-windows
.
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -