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

Bump Kubernetes to 1.25.5 and update manifest accordingly #3973

Merged
merged 7 commits into from
Jan 18, 2023
Merged

Bump Kubernetes to 1.25.5 and update manifest accordingly #3973

merged 7 commits into from
Jan 18, 2023

Conversation

TeddyAndrieux
Copy link
Collaborator

  • PodSecurityPolicy API gets removed in 1.25, so make sure not to use them
  • kube-proxy is now distroless, so rework the way to build the config so that it use an initContainer instead of a sed at kube-proxy container startup
  • Bump Kubernetes to 1.25.5 and update manifests (based on kubeadm)
  • Bump etcd to 3.5.6 and update manifest (based on kubeadm)
  • Bump CoreDNS to 1.9.3 and update manifest (based on kubeadm)

@TeddyAndrieux
salt: Remove no longer needed cleanup state for Prometheus
ae8cefd 
Those resources has been deleted since a long time ago and we do not
support upgrade of more that one major version at once
@TeddyAndrieux
salt: Move old Loki PodSecurityPolicy deletion before upgrade
b7a0c40 
Since the `PodSecurityPolicy` API get removed in Kubernetes 1.25 make
sure to delete it before the upgrade
@TeddyAndrieux
build: Embed alpine image in the registry
ebf8530 
And use this embedded image as base image for `metalk8s-alert-logger` and
`metalk8s-keepalived`
@TeddyAndrieux
salt: Use an initContainer to build kube-proxy config
034b4e4
@TeddyAndrieux
build,salt: Bump Kubernetes to 1.25.5
ad180d9 
Update the manifests accordingly

NOTE: The registry also moved from `k8s.gcr.io` to `registry.k8s.io`
@TeddyAndrieux
build: Bump etcd to 3.5.6
5cc38a3
@TeddyAndrieux TeddyAndrieux requested a review from a team as a code owner January 17, 2023 15:37
@bert-e
Copy link
Contributor

bert-e commented Jan 17, 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 Jan 17, 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:

gdemonet
gdemonet previously approved these changes Jan 18, 2023
View reviewed changes
buildchain/buildchain/constants.py Outdated Show resolved Hide resolved
@TeddyAndrieux TeddyAndrieux force-pushed the improvement/bump-k8s-to-125 branch from 879b97e to 1bae5bc Compare January 18, 2023 08:23
@TeddyAndrieux
Copy link
Collaborator Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Jan 18, 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:

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jan 18, 2023

Build failed

The build for commit did not succeed in branch improvement/bump-k8s-to-125.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jan 18, 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/125.0

The following branches will NOT be impacted:

  • development/123.0
  • development/124.0
  • development/124.1
  • 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 Jan 18, 2023

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

  • ✔️ development/125.0

The following branches have NOT changed:

  • development/123.0
  • development/124.0
  • development/124.1
  • 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 None.

Goodbye teddyandrieux.

@bert-e bert-e merged commit 1bae5bc into development/125.0 Jan 18, 2023
@bert-e bert-e deleted the improvement/bump-k8s-to-125 branch January 18, 2023 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gdemonet gdemonet gdemonet 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.
3 participants
@TeddyAndrieux @bert-e @gdemonet