Oh definitely, everything in kubernetes can be explained (and implemented) with decades-old technology.
The reason why Kubernetes is so special is that it automates it all in a very standardized way. All the vendors come together and support a single API for management which is very easy to write automation for.
There's standard, well-documented "wizards" for creating databases, load-balancers, firewalls, WAFs, reverse proxies, etc. And the management for your containers is extremely robust and extensive with features like automated replicas, health checks, self-healing, 10 different kinds of storage drivers, cpu/memory/disk/gpu allocation, and declarative mountable config files. All of that on top of an extremely secure and standardized API.
With regard for eBPF being used for load-balancers, the company who writes that software, Isovalent, is one of the main maintainers of eBPF in the kernel. A lot of it was written just to support their Kubernetes Cilium CNI. It's used, mainly, so that you can have systems with hundreds or thousands of containers on a single node, each with their own IP address and firewall, etc. IPtables was used for this before. But it started hitting a performance bottleneck for many systems. Everything is automated for you and open-source, so all the ops engineers benefit from the development work of the Isovalent team.
It definitely moves fast, though. I go to kubecon every year, and every year there's a whole new set of technologies that were written in the last year lol
Holding westerners hostage. The more they support Ukraine, the more terrorism westerners face. If they stop supporting Ukraine, the implication is that Russian terrorism would stop.
Ah, but your dns discovery and fail over isn't using the built-in kubernetes Services? Is the nginx using Ingress-nginx or is it custom?
I would definitely look into Ingress or api-gateway, as these are two standards that the kubernetes developers are promoting for reverse proxies. Ingress is older and has more features for things like authentication, but API Gateway is more portable. Both APIs are implemented by a number of implementations, like Nginx, Traefik, Istio, and Project Contour.
It may also be worth creating a second Kubernetes cluster if you're going to be migrating all the services. Flannel is quite old, and there are newer CNIs like Cilium that offer a lot more features like ebpf, ipv6, Wireguard, tracing, etc. (Cilium's implementation of the Gateway API is bugger than other implementations though) Cillium is shaping up to be the new standard networking plugin for Kubernetes, and even Red Hat and AWS are starting to adopt it over their proprietary CNIs.
If you guys are in Europe and are looking for consultants, I freelance, and my employer also has a lot of Kubernetes consulting expertise.
I think most of the western analysts think that this would be a possible compromise. Allowing Russia to hold Crimea and donbass, at least defacto, and Ukraine joins nato to prevent further incursion by Russia.
Literally everyone who didn't vote for Trump was saying this lol
The fact that Trump might be considering security guarantees is honestly kinda promising, though. Letting Ukraine into nato would be the single best broken clock moment this decade. I don't think russia will be in a position to accept that within 100 days, but we can hope.
Ah, interesting. What kind of customization are you using CoreDNS for? If you don't have Ingress/Gateway API for your HTTP traffic, Traefik is likely a good option for adopting it.
Between pods, the universal pattern is to add a Service for your pod(s), and just use the name of the service to connect to the pods the Service is tracking. Internally, the Service is a load-balancer, running on top of Kube-Proxy, or Cilium eBPF, and it tracks all the pods that match the correct labels. It also takes advantage of the Kubelet's health checks to connect/disconnect dying pods. Kubedns/coredns resolves DNS names for all of the Services in the cluster, so you never have to use raw IP addresses in Kubernetes.
I've inherited it on production systems before, automated service discovery and certificate renewal is definitely what admins should have in 2025. I thought the label/annotation system it used on Docker had some ergonomics/documentation issues, but nothing serious.
yeah, imagine how much more efficient the western economies would be if they didn't have this crippling dependency on a trillion dollars of gasoline a year and trillions of dollars worth of cars.
Saudi Arabia and Russia would go broke overnight. Entire government debts would be written off.
The EU and its allies is bigger than Trump's rogue oligarchy