Data

Red Hat’s Quay 3 Container Supports Multiple Architectures

2 May 2019 9:45am, by

Red Hat has released Quay 3, the container image registry it gained in the acquisition of CoreOS in January 2018.

In the latest version, Quay supports multiple architectures, Windows container images, and RHEL-based images.

The company touts Quay at the first private enterprise hosted registry, dating to 2013 (pre-CoreOS), with innovative capabilities including image rollback and zero-downtime garbage collection.

The new support for multiple architectures means users can run containers on more platforms and different systems such as IBM Power LE and Z System workloads, Arm-based IoT devices, and Windows-based workloads.

Support for Windows container images expands its use to those using multiple clouds or Windows-only shops.

The ability to use Red Hat Enterprise Linux-based images means those who want to use Red Hat technology throughout can do so. Quay provides another component to Red Hat’s fully supported container deployment pipeline and a smaller potential attack surface, according to the company.

Quay provides team and organization mapping, CLI password encryption, and meticulous event logging. It contains automated build and lifecycle management features, as well as the ability to scale with geographic replication and higher availability.

Its other security features include support for multiple authentication systems and identity providers as well as vulnerability scanning through integration with the Clair security scanner. Clair is an open source project for static analysis of vulnerabilities in application containers.

Quay is available as enterprise software and as a hosted service at Quay.io.

Users of Red Hat OpenShift must select an image registry to pair with the platform. While OpenShift has an existing registry, Red Hat plans to replace it with Quay, the company said. Red Hat said also it plans to build tighter integration between the two products to improve user experience. Other Quay capabilities in the works include automating mirroring of namespaces, repositories, or a subset of those between multiple registries; enhanced support for storage backends and other content types; as well as content-governance-related enhancements.

How Red Hat would integrate the CoreOS assets has been a topic of speculation, especially around OpenShift and the CoreOS Kubernetes-platform-as a service Tectonic.

Red Hat is a sponsor of The New Stack.

A newsletter digest of the week’s most important stories & analyses.

View / Add Comments

Please stay on topic and be respectful of others. Review our Terms of Use.