User experience design has a significant impact on how smooth your development process is. You shouldn’t have to struggle to work with your registry and orchestration systems; they should complement each other in a way that improves a user’s experience for both. As Kubernetes has exploded in popularity and more people use orchestration, there has been a shift in how users interact with their registries. The Quay team at CoreOS continues to make improvements to the quality of life of those implementing modern best practices for containerized deployments.
Enabling full automation of Kubernetes deployments
Last month, we announced an experimental feature that enables Quay users to push, pull, and discover Helm charts in a way that’s familiar to those working with container images. For this year’s KubeCon Europe attendees, Brandon Philips demonstrated a simple deployment workflow using Quay during his keynote presentation. Since then, the Quay team has been fixing bugs and improving error messages to create a more consistent experience. Managing containerized software at the application level is a brand new experience for the community, and as best practices emerge, the Quay team continues to work with the Kubernetes Apps SIG (Special Interest Group) to create a stable foundation. To demonstrate how all these tools can fit together, we’ve recorded the following video that contains an example end-to-end build and deployment pipeline using the new Quay App Registry:
Striking a balance with our web experience
A new generation of users influenced by orchestration platforms is beginning to interact with Quay. It’s important that Quay’s website strike a balance for users with different workflows and enables the most cohesive experience for all. Some observant Quay users have noticed smaller design changes recently, but now we’re making some larger changes: the addition of an Applications tab in our global header, and the brand new application repository page.
This Prometheus Operator page provides a sample of a cleaner style that removes modal dialogs and unintuitive aspects from previous designs. You can expect additional improvements to our Search and Image Repository pages coming soon.
Polishing enterprise auth
For a wide variety of scenarios, the best solution for users is to run their own instances of Quay on-premises. In these environments, integration with existing internal software becomes key to improving operations and management. In the past few releases, we’ve made major improvements to the authentication capabilities in Quay Enterprise with the goals of expanding the variety of integration options and refining existing integrations. Quay Enterprise now supports configuring a generic OIDC server for authentication; this enables users to log into Quay Enterprise with any service that implements the OpenID Connect protocol, such as PingFederate. For those using Quay Enterprise’s first-class LDAP authentication, superusers will be able to optionally synchronize teams within Quay to LDAP Groups. Team synchronization aims to eliminate the support burden of enterprises managing teams across all of their applications by enabling them to manage them centrally in LDAP.
Learn more at CoreOS Fest
If you want to hear from the Quay team in person about these and other updates, come to CoreOS Fest! There, you’ll have the opportunity to meet some of the Quay team and other members of the open source community. Register today!