tag 0.1.0 release

[BenTheElder]

it's time :-)
fixes #208

[BenTheElder]

really it is past time

[tao12345666333]

LGTM

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, tao12345666333

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[BenTheElder]

this process is sorta goofy, I have to manually push the actual release tag afterwards with my write access anyhow since github doesn't seem to have any other mechanism for that. going to self-merge 🤷‍♂️

[tao12345666333]

@BenTheElder can we add some ci jobs using GitHub API to do this? https://developer.github.com/v3/repos/releases/#create-a-release

we can add one VERSION file and make the ci job watch it for release.

[BenTheElder]

@tao12345666333 creating a release like that requires referencing a tag (tag_name) so I think it won't buy us much. We also still have to push a tag, write the release notes, and post the binaries. I looked at automating more of that but the uploading and tagging part is quick & simple, and automated release notes will not be as good as human curated notes I think :-)

We script (hack/release/create.sh):

• updating the version file
• creating the tag
• building binaries for all platforms
• updating the version file again

Manually:

• PR the version file
• Push the tag
• Create a release entry / write release notes, upload the binaries to that

[BenTheElder]

we are looking at #197 though for automation of the images, and if we do this more often it will take less time to write the notes hopefully :-)

[tao12345666333]

Thanks for your explanation. 👍

[neolit123]

The current kind Config is now at kind.sigs.k8s.io/v1alpha2, with support for multi-node clusters! (thanks @fabriziopandini!)

we should have outlined that multi-node is enabled on the config side, but not in the backend - i.e. WIP?

[BenTheElder]

@neolit123 multi-node should work (?), but not EG HA, external etcd etc.

[neolit123]

hmm, @fabriziopandini could you please comment.
was under the impression that there is still something in the works there.
maybe i should just test myself...

[BenTheElder]

There is some in the works, particularly HA related.

…

On Wed, Jan 16, 2019 at 10:40 AM Lubomir I. Ivanov ***@***.***> wrote: hmm, @fabriziopandini <https://github.com/fabriziopandini> could you please comment. was under the impression that there is still something in the works there. maybe i should just test myself... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#226 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA4Bq31nVP_uQK2QyRzjs_9AEO0M99o4ks5vD3IxgaJpZM4aCSJJ> .

[fabriziopandini]

@BenTheElder @neolit123 we currently support n>1 workers only.
I will send asap a PR for supporting n>1 control-plane nodes (with external LB) which is P0 for kubeadm, while external-etcd IMO is a lower priority.
And after this IMO we can focus on UX