Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automated cherry pick of #66630: Bump to k8s.gcr.io/metadata-proxy:v0.1.10 #66730

Merged
merged 1 commit into from
Jul 31, 2018
Merged

Automated cherry pick of #66630: Bump to k8s.gcr.io/metadata-proxy:v0.1.10 #66730

merged 1 commit into from
Jul 31, 2018

Conversation

dekkagaijin
Copy link
Contributor

Cherry pick of #66630 on release-1.10.

#66630: Bump to k8s.gcr.io/metadata-proxy:v0.1.10

Bump to k8s.gcr.io/metadata-proxy:v0.1.10
545e96f 
Signed-off-by: Jake Sanders <jsand@google.com>
@k8s-ci-robot
Copy link
Contributor

@dekkagaijin: All 'parent' PRs of a cherry-pick PR must have one of the "release-note" or "release-note-action-required" labels, or this PR must follow the standard/parent release note labeling requirement.

The following parent PRs have neither the "release-note" nor the "release-note-action-required" labels: #66630.

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.

@k8s-ci-robot
Copy link
Contributor

@dekkagaijin: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 28, 2018
@k8s-github-robot k8s-github-robot added the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Jul 28, 2018
@neolit123
Copy link
Member

/cc @mikedanese
/cc @foxish
/ok-to-test

@k8s-ci-robot k8s-ci-robot requested a review from foxish July 29, 2018 23:23
@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 29, 2018
@MaciekPytel
Copy link
Contributor

@dekkagaijin Can you add a release note to PR #66630, describing changes or linking to release notes? Note that release notes for cherry-picks are taken from PR to master, not cherry-pick PR.

@MaciekPytel MaciekPytel added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. and removed do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. labels Jul 30, 2018
@dekkagaijin
Copy link
Contributor Author

@MaciekPytel done

@mikedanese
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 30, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dekkagaijin, mikedanese

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:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 30, 2018
@MaciekPytel MaciekPytel added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 31, 2018
@k8s-github-robot
Copy link

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

@k8s-github-robot
Copy link

Automatic merge from submit-queue.

@k8s-github-robot k8s-github-robot merged commit 82a4943 into kubernetes:release-1.10 Jul 31, 2018
@dekkagaijin dekkagaijin deleted the automated-cherry-pick-of-#66630-upstream-release-1.10 branch July 31, 2018 20:03
@wenjiaswe wenjiaswe mentioned this pull request Aug 4, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mikedanese mikedanese Awaiting requested review from mikedanese

@Q-Lee Q-Lee Awaiting requested review from Q-Lee

@foxish foxish Awaiting requested review from foxish

Assignees

@mikedanese mikedanese

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
6 participants
@dekkagaijin @k8s-ci-robot @neolit123 @MaciekPytel @mikedanese @k8s-github-robot