Currently harbor runs on a single VM, with no high availability setup nor disaster recovery.
This task is to define which one we want (or if we want both) and write down the appropriate tasks for them.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Raymond_Ndibe | T336668 [harbor] Create backups and/or replication | |||
| Open | None | T356301 [harbor] Deploy with Helm | |||
| Resolved | Raymond_Ndibe | T350687 [harbor] Move harbor data to object storage service | |||
| Resolved | dcaro | T376673 [openstack object storage] deleted files still occupying space | |||
| Resolved | dcaro | T306820 [ceph] Upgrade to v16 | |||
| Resolved | dcaro | T309789 [ceph] Upgrade hosts to bullseye | |||
| Resolved | dcaro | T369026 [reimage,ceph] reimaging cloudcephosd hosts gets stuck in network configuration screen | |||
| Resolved | Andrew | T383817 partman vs cloudcephosd1012 | |||
| Resolved | None | T396940 cloudcephosd1xxxx.private.eqiad.wikimedia.cloud | |||
| Resolved | dcaro | T398389 ceph-mon 16.2.15+ds-0+deb12u1 uses all the RAM |
Event Timeline
Comment Actions
Not really, it's simpler than that, it's about having some availability with the current setup.
About moving to helm deployment, we would have to consider also if using the same k8s cluster than toolforge or a different one, as that might lead to a chicken-and-egg problem (specially if we start hosting k8s-specific images in the repo).