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.
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Restricted Task | |||||
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 |
Event Timeline
The current images are in https://quay.io/organization/wikimedia-paws-prod/ I can give access to users there, or we can move to a different registry.
@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 :)
I made a quay.io user https://quay.io/user/brookestorm, but I still definitely am interested in the answers to those questions.
From https://quay.io/plans/:
Can I use Quay for free?
Yes! We offer unlimited storage and serving of public repositories. We strongly believe in the open source community and will do what we can to help!
Thank you for doing more than my web drive-by, @bd808! @Chicocvenancio please give me access!
Then I can push up my custom tags for testing in the new cluster. 💃
Got it! I'll close the task since I can then add others if needed. Thank you very much!