-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.2.0 Heapster #32649
v1.2.0 Heapster #32649
Conversation
cc @mwielgus |
@kubernetes/heapster-maintainers |
LGTM |
GCE e2e build/test passed for commit 0f40f94. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 0f40f94. |
Automatic merge from submit-queue |
Commit found in the "release-1.4" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
The change is not included in release-1.4 branch. |
Commit found in the "release-1.4" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
Commit found in the "release-1.4" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
@eparis Something weird is going on here. Would you take a look? |
Commit found in the "release-1.4" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
Maybe this is using the name of the PR? |
Changed the name of the PR to see if it helps |
Commit found in the "release-1.4" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
Automatic merge from submit-queue Bumped Heapster to v1.2.0 ```release-note Bumped Heapster to v1.2.0. More details about the release https://github.com/kubernetes/heapster/releases/tag/v1.2.0 ``` Version `v1.2.0` is a stable release of the previous release candidate `v1.2.0-beta.3`. The only difference is bumped Kubernetes deps to the lastest stable release `v1.4.0-beta.3` kubernetes-retired/heapster#1290. It's low risk change. It may impact HPA and Monitoring e2e tests. (cherry picked from commit 8f4c0bb)
I'm picking it right now into #32717 |
I'll try to figure out what the bot is doing wrong later.... Was anything merged and reverted related to this? |
Not sure. |
Automatic merge from submit-queue Bumped Heapster to v1.2.0 ```release-note Bumped Heapster to v1.2.0. More details about the release https://github.com/kubernetes/heapster/releases/tag/v1.2.0 ``` Version `v1.2.0` is a stable release of the previous release candidate `v1.2.0-beta.3`. The only difference is bumped Kubernetes deps to the lastest stable release `v1.4.0-beta.3` kubernetes-retired/heapster#1290. It's low risk change. It may impact HPA and Monitoring e2e tests. (cherry picked from commit 8f4c0bb)
Version
v1.2.0
is a stable release of the previous release candidatev1.2.0-beta.3
. The only difference is bumped Kubernetes deps to the lastest stable releasev1.4.0-beta.3
kubernetes-retired/heapster#1290.It's low risk change. It may impact HPA and Monitoring e2e tests.
This change is