Use update cluster from create cluster

Don't fail elastic IP task if TagOnSubnet is not set

Turn down no-change logging in dns-controller

Bump to 4.4.41 image, with more regions

We don't yet have a strong strategy for how to handle this if we are
interrupted, but the same problem exists with taggging in general.
Likely we'll need to write something like a WAL-log, and then check for
interrupted in-flight objects next time we run.

In any case, we shouldn't treat not using TagOnSubnet as an error.

We were trying to call but the result was subtly different (because of
different defaulting.)  The two code paths makes testing hard, so just
have one code path.

kops: Always enable CI versioning on gcs-upload-ci target

Follow-on to https://github.com/kubernetes/kops/pull/1380, relies on
https://www.gnu.org/software/make/manual/make.html#Target_002dspecific
to override the target used for CI upload.

Clean up sysctls

Recognize CI=1 to makefile, use git sha for VERSION

Store in v1alpha2 format

Lock down master security group rules

Default bastion name should be bastion.<clusterName>

bastion-<clustername> is not necessarily in the same hosted zone, nor is
bastion-<dnszone>, and bastion-<dnszone> is not necessarily unique
across clusters.

Dial down default protokube logging to 4

Update to dns-controller 1.5.0

kops get clusters should print zones

Unclear labels example, added `spec:` to clarify which section

Support private hosted zones in DNS

The example was missing which section the labels should be added to.

Docs on using the bastion

Remove duplicate key; add missing blank line

The list of subnets just isn't very interesting

dns-controller: don't make spurious updates in buffer

Create a role for networking addons; use as selector

These will be caught later anyway, but we can save a false invalidation
and a spurious log message.

role.kubernetes.io/networking

This ensures that when we switch networking providers, we replace all
the components of the prior tool.

Fix DNS name precreation