Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Fix race condition when waiting for kubeconfig. #357

Merged
merged 1 commit into from
Mar 21, 2017

Conversation

pipejakob
Copy link
Contributor

If WAIT_FOR_KUBECONFIG is set and the cluster comes up very quickly so that first ssh call succeeds, then the output from ssh's initialization (generating keys, showing fingerprints/randomart, etc.) can get included at the start of the kubeconfig.json file, rendering it invalid.

To alleviate this, echo a marker to indicate the start of the file so we can delete this noise.

CC @mikedanese

If WAIT_FOR_KUBECONFIG is set and the cluster comes up very quickly so
that first ssh call succeeds, then the output from ssh's initialization
(generating keys, showing fingerprints/randomart, etc.) can get included
at the start of the kubeconfig.json file, rendering it invalid.

To alleviate this, echo a marker to indicate the start of the file so we
can delete this noise.
@krzyzacy
Copy link

/assign @mikedanese

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Mar 16, 2017
@kerneltime kerneltime merged commit 2b12786 into kubernetes-retired:master Mar 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants