Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add some docs for running kind on GCB #17

Merged
merged 1 commit into from
Nov 10, 2019
Merged

Conversation

hoegaarden
Copy link
Contributor

@hoegaarden hoegaarden changed the title Add some docs for running kind on GCP Add some docs for running kind on GCB Oct 27, 2019
@BenTheElder
Copy link
Contributor

sorry I missed this! thanks!!

- |
curl -L https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl > kubectl
chmod 0750 kubectl
- name: golang
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should consider using the makefile to build (and get version info) or downloading a release binary

however, given the delay on this, I'd say we can think about that in a follow-up

Copy link
Contributor Author

@hoegaarden hoegaarden Nov 11, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which Makefile are you thinking about? sigs.k8s.io/kind/Makefile?

I can look into that.

@BenTheElder BenTheElder merged commit c7b1e36 into kind-ci:master Nov 10, 2019
@hoegaarden
Copy link
Contributor Author

Generally, I think we (or at least I) want to run some tests with the help of kind on GCB as part of the release process (e.g. running a cluster after we ran the branchff). I would guess that we get a better idea of how to successfully/easily run kind on GCB by doing that. I guess we/I will report back here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants