Portworx VS Quay

I would investigate https://openebs.io/ https://portworx.com/ https://longhorn.io/ if you are forced to you can mount ISCSI on the kublet and feed it to one of those solutions. Keep in mind most of the big guys buy some sort of managed solution that you can point a CSI like trident https://netapp-trident.readthedocs.io. Source: almost 2 years ago

Quay.io — Build and store container images with unlimited free public repositories. - Source: dev.to / 3 months ago

The container is built from the repository of MinIO on Quay.io. Port 9000 is used for connecting to the API and port 9001 is for accessing the Console in the browser. - Source: dev.to / 4 months ago

I'd like to extend this functionality to other images also, but I'd prefer not to change manually all the deployments and helm values. Is there a way to implement a transparent caching image registry? I'd prefer something generic, like "everything quay.io to be pulled from harbor.int/quay_cache/". Source: 7 months ago

I have a manifest that has repo's from both quay.io & ghcr.io (Docker & Github I guess) image repositories. Source: 9 months ago

I'm fairly certain that I have the collection installed, I believe my issue is with how it is being referenced. I built Kubernetes AWX first, then the docker EE, I'm pushing it to quay.io and then grabbing the EE for AWX from there. Any thoughts on how I would change the referenced file path, would be very appreciated! Source: 10 months ago