New 'aws-actuator bootstrap` command to bootstrap the kubernetes cluster from scratch

[ingvagabund]

Just run ./bin/aws-actuator bootstrap --manifests examples/ and get:

$ sudo kubectl get nodes
NAME                            STATUS    ROLES     AGE       VERSION
ip-172-31-33-59.ec2.internal    Ready     master    1m        v1.11.2
ip-172-31-35-115.ec2.internal   Ready     <none>    52s       v1.11.2

[ingvagabund]

@enxebre @paulfantom @frobware

[paulfantom]

Cannot we just execute above commands instead of creating bash script user-data.sh just so we can later execute it? If logs are important, we can just use >> to append to log file.

[ingvagabund]

@frobware could tell more how useful that is :)

In case something goes wrong you might want to re-run the shell script without creating a new instance. Anyway, it's still an example and only for demonstration. Not meant to be run in production.

[frobware]

Yeah, I found it useful to rerun.

But I think we also have to be careful -- there's limited value for absolute perfection here as they're really examples and will disappear over time.

[frobware]

Why not aws-actuator? Would naturally yield make aws-actuator.

[ingvagabund]

Fair point. Updated.

[ingvagabund]

/test all

[ingvagabund]

/test e2e

[frobware]

I tried running it:

INFO[0001] Master machine created with ipv4: 172.31.38.217, InstanceId: i-087bc8693bc299a35 

It would be tremendously helpful to print the public IP too.

[ingvagabund]

It would be tremendously helpful to print the public IP too.

Later mate. We need to pull the aws instance status. So I would rather wait until we have that functionality in the code rather than do the mambo jambo in the code. Unless you have a simple way in mind how to do it?

[paulfantom]

/retest

[paulfantom]

/test e2e

[openshift-ci-robot]

@ingvagabund: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/images	82b92cd	link	/test images

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[paulfantom]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, paulfantom

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 [ingvagabund,paulfantom]

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