Why is ipv6 stalling?
IPv6 has been the future for a very long time. The problem is not that it is hard to explain. The problem is that IPv4, NAT, and workarounds are still good enough for most people to avoid the migration pain.
I write about what I've been working on, problems I've solved, and things I'm still trying to figure out.
IPv6 has been the future for a very long time. The problem is not that it is hard to explain. The problem is that IPv4, NAT, and workarounds are still good enough for most people to avoid the migration pain.
I use k9s heavily, so building something similar for NATS keeps sounding like a good idea. I am not convinced yet, but JetStream is the part that makes me pause.
Every EC2 instance exposes the Instance Metadata Service at 169.254.169.254. By default, pods can reach it. They should not and if they need AWS credentials, Pod Identity is the right tool for that.
k8s won't mark a Job complete while any container in the Pod is still running. If you have a logging sidecar that never exits on its own, you need a way to tell k8s it's a helper, not the work itself. That's what native sidecars are for.
JPEG has been the default image format on the web since 1992. AVIF, derived from the AV1 video codec, compresses better at every quality level. The Netflix engineering team benchmarked this. The numbers are significant.