OpenShift Commons Briefing: Quay v3 Release Update and Road Map
July 12, 2019 | by
In this briefing, Dirk Herrmann, Red Hat’s Quay Product Manager walks through Quay v3.0's features, and discusses the road map for future Quay releases, including a progress update on the open sourcing of Quay.
Built for storing container images, Quay offers visibility over images themselves, and can be integrated into your CI/CD pipelines and existing workflows using its API and other automation features. Quay was first released in 2013, as the first enterprise hosted registry. Six years later, we’ve celebrated the first major release of the container registry since it joined the Red Hat portfolio of products through the acquisition of CoreOS in 2018.
Red Hat Quay v3.0 shipped in May, and brought support for multiple architectures, Windows containers, and a Red Hat Enterprise Linux-based image to help users store, build, and deploy their images in a more secure way across diverse enterprise environments. Red Hat Quay v3.1, which is the next major update, will introduce a new repository mirroring feature in addition to the existing Quay geo-replication, and two new operators which should simplify and automate the Quay deployment and improve its integration with OpenShift. In addition to that, we will add support for further backend services and release a bunch of documentation enhancements.
OpenShift Commons builds connections and collaboration across OpenShift and OKD communities, upstream projects, and stakeholders. In doing so we'll enable the success of customers, users, partners, and contributors as we deepen our knowledge and experiences together.
Our goals go beyond code contributions. OpenShift Commons is a place for companies using OpenShift to accelerate its success and adoption. To do this, we'll act as resources for each other, share best practices and provide a forum for peer-to-peer communication.
To stay abreast of all the latest announcements, briefings and events, please join the OpenShift Commons and join our mailing lists & slack channel.
How do you know if something bad is happening in your cluster? How do you know that a node is down, an application isn’t responding, or the storage backing a PVC has “disappeared”? If your answer to ...
The ultimate goal of almost every hacker is to go up. To step up. To grab root, and use it to go higher or lower on the stack, depending upon your perspective. That first foothold is the key element ...