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

Initiate development/126.0 and bump Kubernetes to 1.26.5 #4074

Merged
merged 9 commits into from
Jun 6, 2023
Merged

Initiate development/126.0 and bump Kubernetes to 1.26.5 #4074

merged 9 commits into from
Jun 6, 2023

Conversation

TeddyAndrieux
Copy link
Collaborator

No description provided.

@TeddyAndrieux
Update version to 126.0.0
0285058
@TeddyAndrieux
build,salt: Bump Kubernetes to 1.26.5
6c0cf20
@TeddyAndrieux
salt: Remove bootstrap config update linked to 125.0
d238bb1 
MetalK8s can only be upgraded from one minor at a time, since Control
Plane Ingress handling has been moved from bootstrap config to
ClusterConfig since 125.0.0, let's remove the logic to handle it during
the upgrade
@TeddyAndrieux
Revert "salt: Delete the Loki StatefulSet before upgrade and downgrade"
efa426f 
This reverts commit e686b8b.
@TeddyAndrieux
salt: Remove pre-upgrade job to cleanup Loki
5449a32 
The Loki CronJob to handle auto cleanup has been added since 125.0.0 so
we do no longer need the pre-upgrade job
@TeddyAndrieux
Revert "salt: Cleanup old Loki objects after upgrade and downgrade"
e1ce0eb 
This reverts commit f1387c6.
@TeddyAndrieux
salt: Remove logic to handle migration from MetalLB
2c06cb6 
MetalLB has been removed since 125.0.0 and MetalK8s only support a minor
upgrade at a time, so the logic to handle this migration is no longer
needed
@TeddyAndrieux
salt: Remove logic to handle NodeExporter selector changes
1091d6a 
MetalK8s only support one minor upgrade at once, NodeExporter label
selector change happened since 125.0.0, so remove this logic
@TeddyAndrieux TeddyAndrieux requested a review from a team as a code owner June 6, 2023 13:17
@bert-e
Copy link
Contributor

bert-e commented Jun 6, 2023

Hello teddyandrieux,

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 6, 2023

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:

@TeddyAndrieux
Copy link
Collaborator Author

/approve

@aprucolimartins aprucolimartins self-requested a review June 6, 2023 15:16
@bert-e
Copy link
Contributor

bert-e commented Jun 6, 2023

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/126.0

The following branches will NOT be impacted:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

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 6, 2023

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

  • ✔️ development/126.0

The following branches have NOT changed:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue INIT-126.

Goodbye teddyandrieux.

@bert-e bert-e merged commit 2a8594e into development/126.0 Jun 6, 2023
@bert-e bert-e deleted the improvement/init-126 branch June 6, 2023 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ezekiel-alexrod ezekiel-alexrod ezekiel-alexrod approved these changes

@aprucolimartins aprucolimartins aprucolimartins approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@TeddyAndrieux @bert-e @aprucolimartins @ezekiel-alexrod