4 ms·

I'm regularly getting enquiries but I do DevOps (AWS, Kubernetes and Istio) so I guess my skillset is still in demand. I guess what's more important for me is

I'm regularly getting enquiries but I do DevOps (AWS, Kubernetes and Istio) so I guess my skillset is still in demand. I guess what's more important for me is the type of work. I'm looking for startup work that's a bit more secure now, if that's possible, lol! Doesn't seem so easy to find.

kmac_ 4y ago
Bunch of companies migrate their stack to Kubernetes or other orchestrators (side effect of moving to microservices even when not needed) so you are safe and in demand for long.
- yarky 4y ago
  > even when not needed Examples? Every time I see kubernetes pop up it's because of better performance or lesser costs.
  - k8savu 4y ago
    Anecdotal example, though I'm sure I'm not the only one: We had a C++ service. It needed high availability, but didn't have super high resource requirements. Our setup was an ec2 instance (c5.xlarge) to build and release AMIs (a bash script using debootstrap to build the AMI which someone wrote 10 years ago probably), an autoscaling group of 3 t2.small instances spread across AZs, and an ALB. The total cost of this was perhaps $200/mo, and we had incredibly good uptime. So, what's the catch? Well, it took the service about 20 minutes to build, and about 35 minutes from clicking the "deploy new version" to it actually running. Someone higher up noticed, and a bright-eyed infra engineer said k8s would make the deploy cycle faster. Fast forward a year. Our autoscaling group is now 3 c5.xlarge instances because the kubelet + docker + coredns + all this other k8s gunk I don't understand need significantly more CPU than our app does (and without giving them more CPU, deploy times were much slower since downloading and unpacking the image was so slow). We have a new logging system (our old logging setup wasn't cloud native apparently) that takes a gig more memory per node. A gig of memory per node to support our service, which peaks at 200MiB RSS. Building and deploying a new version still takes about 35 minutes because compiling C++ is the exact same speed in a dockerfile as it is on an ec2 instance. It costs about $600/mo, and it has far more operational load. When it isn't having any issues, the p99 is identical. > better performance or lesser costs It seems like the opposite of what you'd expect. K8s is adding more components. It's adding more resource usage. Why wouldn't that be slower and cost more?
- nunez 4y ago
  this might pick up even more given the VMware/Broadcom acquisition, so you are likely good

kmac_ 4y ago

Bunch of companies migrate their stack to Kubernetes or other orchestrators (side effect of moving to microservices even when not needed) so you are safe and in demand for long.

yarky 4y ago
> even when not needed Examples? Every time I see kubernetes pop up it's because of better performance or lesser costs.
- k8savu 4y ago
  Anecdotal example, though I'm sure I'm not the only one: We had a C++ service. It needed high availability, but didn't have super high resource requirements. Our setup was an ec2 instance (c5.xlarge) to build and release AMIs (a bash script using debootstrap to build the AMI which someone wrote 10 years ago probably), an autoscaling group of 3 t2.small instances spread across AZs, and an ALB. The total cost of this was perhaps $200/mo, and we had incredibly good uptime. So, what's the catch? Well, it took the service about 20 minutes to build, and about 35 minutes from clicking the "deploy new version" to it actually running. Someone higher up noticed, and a bright-eyed infra engineer said k8s would make the deploy cycle faster. Fast forward a year. Our autoscaling group is now 3 c5.xlarge instances because the kubelet + docker + coredns + all this other k8s gunk I don't understand need significantly more CPU than our app does (and without giving them more CPU, deploy times were much slower since downloading and unpacking the image was so slow). We have a new logging system (our old logging setup wasn't cloud native apparently) that takes a gig more memory per node. A gig of memory per node to support our service, which peaks at 200MiB RSS. Building and deploying a new version still takes about 35 minutes because compiling C++ is the exact same speed in a dockerfile as it is on an ec2 instance. It costs about $600/mo, and it has far more operational load. When it isn't having any issues, the p99 is identical. > better performance or lesser costs It seems like the opposite of what you'd expect. K8s is adding more components. It's adding more resource usage. Why wouldn't that be slower and cost more?
nunez 4y ago
this might pick up even more given the VMware/Broadcom acquisition, so you are likely good