From 6c2a775c9bef70bdc9df4eb526bb0e6eb5922db7 Mon Sep 17 00:00:00 2001 From: Ryan Richard Date: Wed, 12 May 2021 11:34:16 -0700 Subject: [PATCH] Use proxy for `pinniped get kubeconfig` in hack/prepare-supervisor-on-kind.sh Because the command now calls the discovery endpoint, so it needs to go through the proxy to resolve the hostname. --- hack/prepare-supervisor-on-kind.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hack/prepare-supervisor-on-kind.sh b/hack/prepare-supervisor-on-kind.sh index 2d7c7d44..8b6d5969 100755 --- a/hack/prepare-supervisor-on-kind.sh +++ b/hack/prepare-supervisor-on-kind.sh @@ -199,7 +199,7 @@ sleep 5 go build ./cmd/pinniped # Use the CLI to get the kubeconfig. Tell it that you don't want the browser to automatically open for logins. -./pinniped get kubeconfig --oidc-skip-browser >kubeconfig +https_proxy="$PINNIPED_TEST_PROXY" no_proxy="127.0.0.1" ./pinniped get kubeconfig --oidc-skip-browser >kubeconfig # Clear the local CLI cache to ensure that the kubectl command below will need to perform a fresh login. rm -f "$HOME/.config/pinniped/sessions.yaml"