WIP: bump k8s to 1.8.0-beta.1

[rphillips]

Issues:

• modify cluster/manifests/kube-system-rbac-role-binding.yaml to use rbac.authorization.k8s.io/v1beta1 instead of v1alpha1
  • v1beta1 changes the selectors to be immutable

[squat]

Awesome

[klausenbusk]

The apiVersion of DaemonSet/Deployment should also be updated.

https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md#major-themes

[klausenbusk]

Should be v1 per the release notes draft: https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md#auth-1

[ericchiang]

Either works. v1alpha1 doesn't anymore due to kubernetes/kubernetes#51839

[ericchiang]

Seeing this error when trying to use this PR

Ignoring json-2.0.3 because its extensions are not built.  Try: gem pristine json --version 2.0.3
Ignoring nokogiri-1.6.8.1 because its extensions are not built.  Try: gem pristine nokogiri --version 1.6.8.1
Starting temporary bootstrap control plane...
Waiting for api-server...
Creating self-hosted assets...
	created          kube-apiserver secret
	created kube-controller-manager poddisruptionbudget
	created kube-controller-manager secret
	created kube-controller-manager deployment
	created                kube-dns deployment
	created                kube-dns service
	created        kube-flannel-cfg configmap
	created          kube-scheduler poddisruptionbudget
	created          kube-scheduler deployment
	created       system:default-sa clusterrolebinding
Error creating assets: [error when creating "/home/core/cluster/manifests/kube-apiserver.yaml": DaemonSet.apps "kube-apiserver" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"k8s-app":"kube-apiserver", "tier":"control-plane"}: `selector` does not match template `labels`, error when creating "/home/core/cluster/manifests/kube-flannel.yaml": DaemonSet.apps "kube-flannel" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"k8s-app":"flannel", "tier":"node"}: `selector` does not match template `labels`, error when creating "/home/core/cluster/manifests/kube-proxy.yaml": DaemonSet.apps "kube-proxy" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"k8s-app":"kube-proxy", "tier":"node"}: `selector` does not match template `labels`, error when creating "/home/core/cluster/manifests/pod-checkpointer.yaml": DaemonSet.apps "pod-checkpointer" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"tier":"control-plane", "k8s-app":"pod-checkpointer"}: `selector` does not match template `labels`]

NOTE: Bootkube failed to create some cluster assets. It is important that manifest errors are resolved and resubmitted to the apiserver.
For example, after resolving issues: kubectl create -f <failed-manifest>

	Pod Status: kube-controller-manager	Pending
	Pod Status:        pod-checkpointer	DoesNotExist
	Pod Status:          kube-apiserver	DoesNotExist
	Pod Status:          kube-scheduler	Pending

edit: removing the daemonsets commits fixed this.

[rphillips]

Reproduced... It has something to do with defaulting labels now. Looking into it.

Reference

[rphillips]

@ericchiang fixed... updated the selectors on the daemonsets.

[dghubble]

Look for CalicoNodeTemplate when you rebase, this was renamed on master

[coreosbot]

Can one of the admins verify this patch?

[ericchiang]

@rphillips can we update this PR now that 1.8 is out? (cc @squat)

[squat]

1.8.0 hyperkube is about to get cut. Waiting for the necessary LGTM and it will be available. xref coreos/kubernetes#167

[rphillips]

yep.. then I'll tweak this PR to remove the API bumps, and do a migration of the APIs in a separate PR

[rphillips]

closing in favor of #729