Some people find difficult to set boundaries. And some other people are always testing the boundaries. When you have both types in the same group this will happen.

I’m not judging, there may be legit, or at least understandable reasons for both behaviours, it is just something I have seen often.

That seems to be US specific. I’ve been pestered by recruiters since late 2025, almost to the 2022 levels.

From the docs in GitHub: “The size of the dots corresponds to the number of reviewed papers for literature reviews (non-reviews have the smallest size)…”

In k8s, being able to use things like External DNS and automatically and declaratively manage DNS entries with code saves so much time you won’t want to go back once you get used to it.

It takes a while to get your head sorted around it and also to deploy but automagically having your DNS entries, your certificates, et etc sorted feels great.

You hired this guy to do new things, let him do them (as a PoC)

Congratulations!

I see this as the EU moving pieces to influence the UK people to revert brexit in a generation (Bregret? Breback?). It benefits the demographic that was already against brexit and keeps the idea od Europe in their minds.

I doubt is for cheap labor. I work in London and in a team of 20 we have a single British, and the few in the company tend to have an easier path for leadership, so why leave? That has been similar in all my previous jobs.

Best I have used is Flux with helmrelease objects and kustomize. Only lacking some UI to get flux events and logs together. I guess that Argocd can do the same with application onjects using charts as source but haven’t tested it yet

But managing both k8s external components (external-dns, external-secrests, CSI, etc etc) and your own apps with kustomizable charts makes so much more sense than having thousand of manifests that I would recommend everyone to try.

If I could be bothered to sit and write down a distilled version of my last decade at work it would be something very similar. Any junior SRE can benefit from this.

I like helm and I think the main reason is that I have way less exposure to helm internals than you.

Helm seems to be designed to follow the write-once-apply-everwhere principle. My experience is

• find a promising k8s tool
• get the chart
• read the values file
• apply (as a flux helm release object)

I almost never need to untar and check the templates, helm for me is an easy to use high level abstraction.

I guess that’s why they sell it as a package manager. The experience of writing the chart sounds dreadful, but using it is mostly trivial.