Deploy new configuration to PAWS-beta first and test basic features. Task to note PAWS-Beta specific developments.
Description
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 | |||
| Declined | None | T218152 Test new configuration in PAWS-Beta |
Event Timeline
Comment Actions
https://paws-beta.wmflabs.org/ seems to be an inexistent . The cluster is not accepting my certificates on toolsbeta-paws-master-01. I can deal with this once Horizon starts playing nice again.
Comment Actions
With the work in T195217: Simplify ingress methods for PAWS and the ability to deploy manually via helm3, we should be able to deploy a beta deployment in a separate namespace of beta in the paws project cluster. I hope to add to the helm chart the ability to simply deploy locally and hopefully also to deploy a beta version for testing in the same cluster.
Comment Actions
It doesn't appear that the beta cluster exists at this point.
paws-beta.wmflabs.org has address 185.15.56.58
185.15.56.58 is assigned to paws, but is listed as unused
Please re-open if applicable.