The quay.io setup seems to integrate well with the workflow established in PAWS. If we keep that, this ticket is to figure out any access concerns or if we can easily manually set some tags there in order to deploy this in the new cluster.
|Resolved||Bstorm||T246122 Upgrade the Toolforge Kubernetes cluster to v1.16|
|Resolved||Bstorm||T211096 PAWS: Rebuild and upgrade Kubernetes|
|Duplicate||• Chicocvenancio||T218150 Update PAWS with Zero to JupyterHub k8s 0.8.0 chart|
|Resolved||aborrero||T195217 Simplify ingress methods for PAWS|
|Resolved||Bstorm||T253702 Figure out storing images for PAWS|
@Chicocvenancio What are the terms on that registry? Is it free? It looks like somebody is paying for it.
Overall, it looks like a good place to keep things, and I'd like access. I just don't want to inadvertently cost someone money if that's charging someone other than the Foundation. I also don't want someone to stop paying for it suddenly if we continue depending on it :)