Red Hat Quay is a private container registry that stores, builds, and deploys container images. It analyzes your images for security vulnerabilities, identifying potential issues that can help you mitigate security risks.
We use Red Hat Quay as a single source of truth for all of our container images. We store all the container images that are used in the OpenShift platform.
We have a mechanism to create organizations on the Quay registry where we can segregate repositories based on business needs and verticals. This helps put more controls in place so that not all cloud users have access to all repositories. We can control it better. User management in Quay, when we manage the repositories using organizations, is more efficient.
It's pretty user-friendly. It's operator-based, and there's no complication in setting it up. Things like downloading an image, pulling an image, tagging, and pushing it back to the needed organization are fairly easy compared to doing things through the command-line interface.
Red Hat is constantly improving its product. Every new version rollout comes with updates that enhance performance. One example is that we used to experience issues when clicking on a repository if we had thousands of them in the registry. In the latest versions, those things have been taken care of.
From the AI perspective, it just serves as a container registry at this point.
We are also looking for the possibility to retain a VM image from Quay, which is not possible currently.
So, nothing is happening regarding AI. I don’t see the role of AI currently.
I have been using it for two to three years now.
I have been working with Red Hat products for quite a long time now. Overall, I have been working with their products for more than seven to eight years. So I’m pretty comfortable with their support. They are able to cater to our needs and respond to our product defects. So far, so good.
Support-wise, every product is assigned a dedicated technical account manager. They have been able to take care of our needs from a support perspective.
Positive
I’ve used the internally managed registry that comes with OpenShift. The internal registry is specific to the cluster, where outsiders cannot access the registry. Of course, if we take care of the network barriers, they can access it, but there will be some security concerns for outsiders to access the registry when it is internal.
Quay being an external registry, all other platforms, like JKS and GKE, can still use Quay registry to store their images.
We do have JFrog and OpenShift in our environment.
I would rate my experience with the initial setup an eight out of ten, with one being difficult and ten being easy.
It’s just a matter of two to three hours, provided you have your OpenShift platform up and running.
Only one person can handle it as long as the prerequisites are in place. You need to ensure that the storage mount points are set up correctly.
Only one person can handle it as long as the prerequisites are in place. It's all a matter of those prerequisites, so we have the application in place. You need to ensure that the storage mount points are in place and that the application is enabled in the backend by the storage team. We've got PostgreSQL being used as a database. So once we have those prerequisites in place, setting it up is fairly easy, and one person can do the job from the front end.
Maintenance is obviously part of operations support. The entire operations team will be supporting it. We have ten-plus members in the team.
We have data operations, like creating organizations and managing the Red Hat Quay registry. We also download the needed reports and upload the reports to the needed organizations based on business needs.
Additionally, we grant and manage rights for the organizations to allow service accounts to pull the image through the CI/CD pipeline.
It is fairly easy to use. It doesn’t take much time to introduce Quay registry to the business units. Anybody who wants to use it as a primary registry just needs to create the organization and move all the images into the respective organization. So, on that front, it is pretty easy to use and faster to deliver to the clients.
I would definitely recommend it.
Overall, I would rate this product an eight out of ten.
