This repository has been archived by the owner on Mar 9, 2022. It is now read-only.
cri-containerd v1.0.0-beta.1 release
·
1281 commits
to master
since this release
SHA256: 86b2415d9fe3b55ef72e290a7dd68adb956a5a8ab7ea58b4271348f30e23324e
Welcome to the v1.0.0-beta.1 release of cri-containerd
!
Note: This repository will be moved into containerd organization after this release.
Highlights
This release we mainly focused on bug fix. Notable bug fixes:
- Get rid of default
RLIMIT_NOFILE
for containers. (Issue: #515, PR: #516, @Random-Liu) - Fix an issue that privileged pod can't run on kernel with version <3.16. (Issue: #517, PR: #518, @Random-Liu)
- Cache pod IP for performance and also unblock VM-based container support. (Issue: #524, PR: #525, @abhi)
- Add a flag
skip-imagefs-uuid
to skip retrieving image filesystem UUID. Users will be able to trycri-containerd
on node withmdev
orZFS
. Note: kubelet will not be able to get imagefs capacity or perform imagefs disk eviction whenskip-imagefs-uuid=true
. (Issue: #325, #399, #509, PR: #510, @Random-Liu)
Test dashboard: https://k8s-testgrid.appspot.com/sig-node-containerd.
External Dependencies
- containerd: v1.0.0
- runc: 74a17296470088de3805e138d3d87c62e613dfc4
- cni: v0.6.0
- Kubernetes: v1.9+ (cri-containerd v1.0.0-beta.1)
- crictl: v1.0.0.alpha.0
Note: Because of Kubernetes container runtime interface change, cri-containerd v1.0.0-beta.1 requires Kubernetes v1.9 or later. With older Kubernetes version, container exec has known issue #417, and container logging won't work.
Try It Out
- For a production quality cluster on GCE brought up with
kube-up.sh
, see here. - For a multi-node cluster installer and bring up steps using ansible and kubeadm, see here.
- For creating a cluster from scratch on Google Cloud, see Kubernetes the Hard Way.
- For a custom installation from release tarball, see here.
- For a installation with LinuxKit on a local VM, see here.
Contributors
We'd like to extend a thanks to the following people who contributed to this release: