Bumped Heapster version to 1.4.3

[loburm]

Bumped Heapster version to 1.4.3 - more details https://github.com/kubernetes/heapster/releases/tag/v1.4.3.

[loburm]

/assign @piosz @wojtek-t

[piosz]

/lgtm
/approve no-issue

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: loburm, piosz

Associated issue requirement bypassed by: piosz

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

Needs approval from an approver in each of these OWNERS Files:

• cluster/addons/cluster-monitoring/OWNERS [piosz]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[loburm]

/assign @jpbetz

[piosz]

@jpbetz to give you more context: we didn't manage to release the stable version of Heapster 1.5 before Kubernetes 1.8, so reverting to the previous stable version.

[liggitt]

@jpbetz to give you more context: we didn't manage to release the stable version of Heapster 1.5 before Kubernetes 1.8, so reverting to the previous stable version.

how risky is this change? there's a fair number of issues pending a 1.8.1 release... is this going to extend the time we need to soak before cutting a 1.8.x release?

[jpbetz]

@piosz Would you please summarize what happens when a k8s cluster running heapster-v1.5.0-beta.0 is downgraded to heapster-v1.4.3. Has this been tested? Are there any steps cluster operators would need to take?

[piosz]

@liggitt low risk change - Heapster 1.4.3 is well tested with Kubernetes 1.7.
@jpbetz no action required. Heapster is almost stateless (it remembers the latest value of metrics) and doesn't have any API, so nothing should happen in case of downgrade, except from a short downtime window (up to 2 minutes) for horizontal pod autoscaler, which basically happens during every Heapster restart.

[piosz]

@jpbetz ping

[jpbetz]

We're about to cut release 1.8.1. We are minimizing the cherry picks we accept to keep the branch stable. If this is a critical fix, please let me know and I'll review, otherwise it will be cherry picked for 1.8.2. Thanks!

[piosz]

@jpbetz yes, please include this is 1.8.1

[jpbetz]

/approved

[jpbetz]

Looks like the pull-kubernetes-e2e-kubeadm-gce test is not progressing due to kubernetes/test-infra#4912. Looking in how to mitigate this now.

[jpbetz]

/test pull-kubernetes-e2e-kubeadm-gce

[jpbetz]

/test pull-kubernetes-e2e-kubeadm-gce

[jpbetz]

/test pull-kubernetes-e2e-kubeadm-gce

[k8s-ci-robot]

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

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-kubeadm-gce	96d591f	link	/test pull-kubernetes-e2e-kubeadm-gce

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.

[jpbetz]

/test pull-kubernetes-e2e-gce-etcd3

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[k8s-github-robot]

Automatic merge from submit-queue.

[k8s-cherrypick-bot]

Commit found in the "release-1.8" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked.