We are happy to announce the release of CRI-O v1.0.0-rc2
Big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM and others.

The main reason behind this second RC is to fix a failure to pull official images from the Docker Hub.
Highlights of the release:

• Fix image pulling.
  Docker Hub started serving manifest lists for different architectures for official images (e.g. redis). That resulted in CRI-O not being able to pull official images from Docker Hub.
• Correctly set hostname in pods.
• SELinux fixes.
• Updated kubernetes to v1.7.6.
• Fixes to seccomp handling.
• Other fixes and more tests.

List of changes is available here https://github.com/kubernetes-incubator/cri-o/compare/v1.0.0-rc1...v1.0.0-rc2?expand=1

Highlights of the release:

• Bugs, stability and performance fixes
• Moved from kubernetes 1.6 to 1.7
• cadvisor isupport
• Full kube e2e tests coverage. We are now gating pull requests on kube e2e (we were gating them just on node-e2e).
• Continue working on kpod. New commands added:
  • kpod cp
  • kpod diff
  • kpod export
  • kpod logs
  • kpod mount
  • kpod ps
  • kpod rename
  • kpod stats
  • kpod umount

This release contains minor features improvements as we’re totally focused on bugs, stability and, above all, performance fixes for 1.0.0.
List of changes is available here https://github.com/kubernetes-incubator/cri-o/compare/v1.0.0-beta.0...v1.0.0-rc1?expand=1

We are happy to announce the release of CRI-O v1.0.0.beta.0
Big thanks to our maintainers and contributors from Red Hat, Intel, SUSE, Hyper, IBM and others.

Highlights of the release:

• OCI 1.0 runtime and image specifications support
• Additional registry support
• Daemon pids-limit support
  cri-o daemon now supports a default pid-limit on all containers to prevent fork-bombs. This is configurable by admins through a flag or /etc/crio/crio.conf
• Configurable image volume support
• Bugs and Stability fixes

We are continuing to focus on bugs and stability improvements for 1.0.

Thanks,
CRI-O team.

With this release, we are passing all the k8s’s e2e tests.

Highlights of the release:

• All e2e tests pass.
• Attach/detach support.
• OOM detection.
• Kubeadm integration.
• Networking tested with Weave, Flannel and openshift-sdn.
• Lots of bug and stability fixes.

We are now focused on bugs and stability to release 1.0. We’re also working to have native RPMs and debs for all major operating systems.
In case you’re looking to help us testing and debugging we do have an handy ansible playbook to get CRI-O installed from source and ready to provision a kubernetes cluster with kubeadm.

With this release, we are passing all the k8s’s node conformance tests.

Highlights of the release:

1. Streaming exec support
2. Port forwarding support
3. Lots of bug fixes

Features that don't work yet:

1. Attach

With this release, we have made good progress on passing the node conformance tests.

Highlights of the release:

1. Logging support
2. 115/121 (95%) node conformance tests pass (#441)
3. gpg check on image pull
4. Lots of bug fixes
5. Supports latest runc v1.0.0-rc3 and runtime-spec v1.0.0-rc5

Features that don't work yet:
Streaming (exec), attach and port forward.

We are able to run a k8s cluster with cri-o and run basic pods with this release.

Features:

1. Pod lifecycle
2. Container lifecycle
3. Image lifecycle
4. CNI networking integration
5. Exec (sync)
6. Support for restarting the daemon
7. Support for multiple storage backend drivers (overlay, devicemapper, aufs, btrfs)
8. SELinux support
9. Seccomp support (partial)
10. Clear Containers support

Features that don’t work yet:
Logging (should be available shortly in 0.2)
Exec (streaming)
Attach
Port-forwarding