There are now two new Toolforge Kubernetes workers in service,
tools-k8s-worker-nfs-1 and tools-k8s-worker-nfs-2. In addition to the new
naming scheme that will allow non-NFS workers in the future, these hosts
are also running Debian 12 (as opposed to Debian 10 on the existing nodes)
and are using Containerd as the container runtime (the current nodes are
using Docker).
If you see or hear about any strange issues on pods running on these new
nodes, please depool them (`kubectl sudo drain $WORKER` on a Toolforge
bastion) and ping me on IRC or in the task (
https://phabricator.wikimedia.org/T284656).
If there are no major issues I will start replacing more of the older nodes
with these new nodes next week.
Taavi
--
Taavi Väänänen (he/him)
Site Reliability Engineer, Cloud Services
Wikimedia Foundation
Hi all!
Lately we released the public beta for the build service, that allows users
to build images from their language of choice package manager settings (for
supported languages), with minimal configuration.
While we are still fixing bugs and corner cases, we should start thinking
on the next steps for toolforge.
I have started a document with some ideas on how toolforge could look like
in the future for users, and I want to gather other ideas and feedback so
we can write down a high level view to help define the next round of
improvements to focus on.
The document is here:
https://docs.google.com/document/d/1sqo6YGRn9u-S7V0y9m07cYKA84vQlKa-7_F8p7e…
And it already takes some of the ideas from previous documents/meetings/etc.
The timeline is to brainstorm there until Tuesday next week, and then in
the Toolforge Workgroup check-in we can start trying to coalesce the main
ideas to a workable plan.
Note that this is not meant to be written on stone, but instead we will
review it a couple times a year to make sure that we are doing what we want
to do, and change course if needed.
Thanks!