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

Use the same version of the pause image for all container runtimes #49296

Closed
afbjorklund opened this issue Jan 6, 2025 · 4 comments · Fixed by #49297
Closed

Use the same version of the pause image for all container runtimes #49296

afbjorklund opened this issue Jan 6, 2025 · 4 comments · Fixed by #49297
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@afbjorklund
Copy link
Contributor

afbjorklund commented Jan 6, 2025

This is a Bug Report

Problem:

Currently different container runtimes are using different versions of the pause image, in their configuration.

Proposed Solution:

The pause image version should match what kubeadm checks for, which might vary by the Kubernetes version.

Page to Update:

https://kubernetes.io/docs/setup/production-environment/container-runtimes/

container runtime sandbox image
containerd registry.k8s.io/pause:3.2
cri-o registry.k8s.io/pause:3.6
docker (default, it currently uses 3.9*)

* currently docker is missing the information, what value to use for cri-dockerd

Additional Information:

#48976 (comment)

@afbjorklund afbjorklund added the kind/bug Categorizes issue or PR as related to a bug. label Jan 6, 2025
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 6, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

@dims
Copy link
Member

dims commented Jan 6, 2025

@afbjorklund can you please cut a PR to update that reference to 3.10 instead?

thanks!

@afbjorklund
Copy link
Contributor Author

afbjorklund commented Jan 6, 2025

I think it would need some kind of constant, to match k8s version and to not miss 3.11?

Since kubeadm checks for a particular version, the documentation should reflect that.

detected that the sandbox image "" of the container runtime is inconsistent with that used by kubeadm.
It is recommended to use "registry.k8s.io/pause:3.10" as the CRI sandbox image. 

And then I guess it needs some kind of blurb for docker systemd config, ExecStart etc

@afbjorklund
Copy link
Contributor Author

Added an issue for cri-dockerd, to update the pause image to the same as everyone else:

The default should be fine for supported versions of containerd and cri-o, without config.

It was just that the Kubernetes documentation (previously) suggested downgrading them...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants