Lemmy.World is looking for 4 new Systems operators to help with our growing community.
Volunteers will assist our existing systems team with monitoring and maintenance.
We’re ideally looking for chill folks that want to give back to their community and work on our back-end infrastructure. Must have 4+ years of professional experience working in systems administration. We are not looking for junior admins at this time. Please keep in mind that, while this is a volunteer gig, we would ask you to be able to help at least 5-10 hours a week. We also understand this is a hobby and that family and work comes first.
Applicants must be okay with providing their CV and/or LinkedIn profile AND sitting for a video interview. This is due to the sensitivity of the infrastructure you will have access to.
We are an international team that works from both North America EST time (-4) and Europe CEST (+2) so we would ask that candidates be flexible with their availability.
If you are in AEST (+10) or JST (+9) please let us know, as we are looking for at least one Sysadmin to help out during our overnight.
You may be asked to participate in an on-call pool. Please keep in mind that this is a round-robin style pool, so it’s alright if you’re busy as it will just move along the chain.
If you’re interested and want to apply, click here.
A CTO of 5 years with many more years of experience here. I would be really glad to help, but not in scenario where I have to prepare a CV for international readers and have no pay at all as this looks to me like a job application with no job.
Considering you are running on Digitalocean infrastructure, I am completely unsure why you would ever need Ansible and Terraform as it just adds complexity without certain benefit, especially if you mention Kubernetes which DO already provides with two clicks.
I’d personally suggest trying out ArgoCD for declarative clusters. With this thing, I’ve seen 2 companies maintained by a single DevOps engineer with no problems. Huge timesaver and makes everything transparent.
In case this process changes and becomes less corporate-y and more transparent, I’ll be ready to apply. Hope you’re going to find the right people! Long live Lemmy World!
Ansible/Teraform are portable. I don’t see it’s usage as a failing, rather as avoiding DO lock in.
Agreed with the rest though. This is quite the ask.
I’m a big fan of Kubernetes, and for larger projects the flexibility and power it brings is unrivalled. But for smaller projects, assuming equal levels of competence, delivery teams using managed Kubernetes are almost universally later and have more issues than teams that use simpler solutions. Container-as-a-service solutions like GCP CloudRun or AWS FarGate help somewhat, but are not cheap for a given amount of compute time.
Terraform (or IaC in general) absolutely has a place, because even if you use Kubernetes, most projects have more infrastructure to manage than just the cluster - at the very least, lemmy.world has a CloudFlare proxy to manage - and clicking buttons in a management portal is not a repeatable way of deploying that, or deploying the Kubernetes clusters themselves.
Ansible also has a place, particularly if you’re deploying onto bare metal. I wouldn’t use it for new deployments unless I had bare metal to configure and maintain, but lemmy.world is deployed onto a bare metal server as I understand it. Plus, the most effective tooling is generally the one your team understands.
IaC is the right move. It transfers complexity, it necessarilt doesn’t add it. It makes your deployments reproduceable and automated.
Which is a baseline to having highly available infrastructure. Not everyone will be familiar, or have the right mindset for that sort of DevOps.