Always create /var/lib/kubelet, even in bootstrap mode

[justinsb]

Otherwise we end up with a circular dependency where we don't run the
node-authorizer until /var/lib/kubelet has been bind-mounted, but it
can't be bind-mounted until it exists.

This bind-mounting happens on Google's ContainerOS, which is why it
isn't always seen.

[chrisz100]

/lgtm

It can be so simple to stop crazy things from happening 🤟🏼

[justinsb]

/retest

Doesn't look entirely unrelated - mount propagation in /var/lib/kubelet. Maybe the file mode. Retesting to get more signal...

[gambol99]

/test pull-kops-e2e-kubernetes-aws

[justinsb]

Changing the directory mode to 755 - I'm guessing the permissions were causing the mount propagation errors.

[justinsb]

/retest

The zone selection fix merged in test-infra, just checking if it's live...

[justinsb]

Moving to 1.12 milestone - no need for this in 1.11 I don't think

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb

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 [justinsb]

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

[chrisz100]

/lgtm