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.

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

build: bump k8s version to 1.16.10 #2597

Merged

Conversation

Ebaneck
Copy link
Contributor

@Ebaneck Ebaneck commented Jun 4, 2020

Component:

'kubernetes', 'build'

Context:

See #2590

Summary:

Update the k8s version and it's components to the most recent patch release.

Acceptance criteria:


Closes: #2590

Update the k8s version and it's components
to the most recent patch release.

Closes: #2590
@Ebaneck Ebaneck requested a review from a team June 4, 2020 09:14
@bert-e
Copy link
Contributor

bert-e commented Jun 4, 2020

Hello ebaneck,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Jun 4, 2020

Conflict

A conflict has been raised during the creation of
integration branch w/2.6/improvement/2590-bump-k8s-version-to-1.16.10 with contents from improvement/2590-bump-k8s-version-to-1.16.10
and development/2.6.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/2.6/improvement/2590-bump-k8s-version-to-1.16.10 origin/development/2.6
 $ git merge origin/improvement/2590-bump-k8s-version-to-1.16.10
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/2.6/improvement/2590-bump-k8s-version-to-1.16.10

@bert-e
Copy link
Contributor

bert-e commented Jun 4, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@Ebaneck
Copy link
Contributor Author

Ebaneck commented Jun 4, 2020

/approve

@bert-e
Copy link
Contributor

bert-e commented Jun 4, 2020

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: approve

@Ebaneck
Copy link
Contributor Author

Ebaneck commented Jun 4, 2020

/approve

@bert-e
Copy link
Contributor

bert-e commented Jun 4, 2020

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/2.5

  • ✔️ development/2.6

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jun 4, 2020

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.5

  • ✔️ development/2.6

The following branches have NOT changed:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4

Please check the status of the associated issue None.

Goodbye ebaneck.

@bert-e bert-e merged commit 44a7abc into development/2.5 Jun 4, 2020
@bert-e bert-e deleted the improvement/2590-bump-k8s-version-to-1.16.10 branch June 4, 2020 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants