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.
I'm curious what the backend looks like based on your requirements here... Ansible is always a red flag for me that your servers are pets not cattle. Just maintain a golden image, especially since you mention kubernetes. And if you're using self managed kubernetes USE REMOTE ETCD. Trust me, it will save you so much time and drama.
I wouldn't be interested unless it's paid so I am just throwing that out there for y'all to consider.
This made me laugh. Configuration management systems like ansible, chef, salt, and puppet only exist because people wanted to manage a large numbers of systems and keep them consistent and replaceable, i.e treat them like cattle instead of pets. They were born out of the pets vs cattle analogy.
I realize containerization has taken that a step further but it's funny to hear someone talk about these tools like they're something archaic.
Probably more accurate to say "mutable" vs "immutable".
Harder to have pets in immutable if it's actually immutable.
If you want to replace them why would you not use a golden image? The same thing goes for VMs, not only containerized. You can sit there and wait for ansible to run, or just have your image come up immediately with what you need. It makes it take longer with 0 benefit.
And where do you think the golden images come from? The steps must be reproducible, versioned, audited, scripted and in the third hands of outsourced minions with 8 or 12h time lapse.
The golden rule of CICD does it survive if you're visited by truck-kun?