X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org AEF34395ACD3
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1592112622;
	bh=L3E45/gJcZPp/Um9Y0i5sYKRzS8ng/m5jHYtrSOkHYs=;
	h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=HeXcCsCMQACr3RKgLxcfnmf0Q2tg+XJ1ICoauxZQHpwCgK9PNsIIlFKecImRNHZPU
	h67phdstoUkiVtwsmJFG4RcgzMJnffpbFUwLGQSAnS/kpUVWwvGyyTnYARYbhjYnjV
	rYyes/BisfkVoybDE5zRSnLoFotwd4bfLqTzELs4=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 1A6C9386F81C
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-language
	:content-transfer-encoding;
	bh=UPBfNSjAChkt6etl+pObOGobTeldpWGzzO3f7tsxVZs=;
	b=YIW2l1kPU2vl6noXsWmBevjKH/yfQgeMkwMzNcptJMmgd2WKUTYyiWlgVOCZtOobQN
	FaZlgiB7m6l0GURnvWWN71X3oGkUe2V3MEU4YQN0+/A/aaFegJhSfyClR2gnmFfGDD+S
	Bq8bwU8OIhIOemsGY8vS9re/7x73OhrVyhxBf0ZTvydYLyGwEAH3+6i51+op5NP8O8DH
	8Ia82Q9FtvYNCkvwu36ikXyDsGzqaWq16ZTAD771TGf7Dk2SHxKQJ9zKd+RB3zSPnZQC
	STSmIQJF9nGjb3uy//PFc+JTwSo0OdU+FY7AsxQON+HoMnK+V0uPT1PWgUEqjG1mQWIP
	veGw==
X-Gm-Message-State:	AOAM531dQbaFvbNcbJnJ/HFIDEGMPox2isR1XA29xK30nPJWtFva08j6
	IbtnWYhBe9ya9gd4qcDjkgV/uMxv
X-Google-Smtp-Source:	ABdhPJyYiDD5cgt1zBDlTCqLzWwn4ihefETxFC6MbrOzCjEHF+0kZsMnjrEhRmu7scP8MNJVvlO9sA==
X-Received:	by 2002:a05:600c:218b:: with SMTP id
	e11mr6787387wme.162.1592112619038;
	Sat, 13 Jun 2020 22:30:19 -0700 (PDT)
Subject:	Re: "kubectl exec" in Cygwin gets "Upgrade request required", but not
	in cmd shell
To:	cygwin AT cygwin DOT com
References:	<CAA5t8VqpU2KiQ_Kk5czjLzeCDzf21Gb2iBLu25xB43ZhpfmaPQ AT mail DOT gmail DOT com>
Message-ID:	<b68e371b-4e3d-3ab3-9a0e-2461697d814d@gmail.com>
Date:	Sun, 14 Jun 2020 07:30:14 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.9.0
MIME-Version:	1.0
In-Reply-To:	<CAA5t8VqpU2KiQ_Kk5czjLzeCDzf21Gb2iBLu25xB43ZhpfmaPQ@mail.gmail.com>
X-Spam-Status:	No, score=-2.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
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:	Marco Atzeri via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

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

--
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 -