djpbessems
/
ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Ryan Richard 2021-05-12 11:34:16 -07:00
parent 41d3e3b6ec
commit 6c2a775c9b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
hack/prepare-supervisor-on-kind.sh
View File

@ -199,7 +199,7 @@ sleep 5
go build ./cmd/pinniped 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. # 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. # 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" rm -f "$HOME/.config/pinniped/sessions.yaml"