llama052

9 ms·

61.
by llama052 2y ago
I think that's the issue, it's not the tooling. Kubernetes is great... unfortunately people are awful at unpacking the underlying layers.
62.
by llama052 2y ago
I'll start by saying that I think knowledge for knowing layers underneath the application is fading in some circles, and that makes me sad. Having been a frontend guy some 10+ years ago, into a network engineer, then infrastructure eng
63.
by llama052 2y ago
This looks like an interesting take on package management. Would be cool for homebrew clusters and the like. However things like helmfile with renovate paired with a pipeline is my personal preference even if just for ensuring things remain
64.
by llama052 3y ago
I wouldn't say this is a problem specific to kubernetes. Most places over-provision their virtual machines also, if not more so due to the less dynamic state of the lower layers.
65.
by llama052 3y ago
It's been the opposite for us. No more waiting for VMs to get spun up and it actually enforces a consistent layer across infrastructure. I'd be curious what the pain you've seen is.
66.
by llama052 3y ago
Girlfriend has lost her entire sense of smell after covid, I'm really hoping the future has an answer to that. It's taken the joy out of a lot of things she enjoys, especially cooking. She's seen a few ENT doctors and they al
67.
by llama052 3y ago
I think it's definitely overlooked. You should always have the ability to spin off a new cluster and run your workloads on that. At a minimum as a disaster recovery scenario.
68.
by llama052 3y ago
That doesn't sound like a devops problem, but a culture one.
69.
by llama052 3y ago
Maybe in FAANG it's "back like we are in 2015" but the tools that have been brought into the mainstream like Kubernetes, automation tools and such have had a great impact across many small to large sized organizations. It&#x2
70.
by llama052 3y ago
We are using Cloudflare enterprise as well and have a phone number to call, including an SLA for P1 support tickets, which I believe is 2 hours. [0] Never had any issues with receiving solid support but our account manager has been super go
71.
by llama052 3y ago
is using your own headers for date not the solution here? I'd imagine a lot of proxies in general will overwrite that date. At least on the corporate proxy side of things.
72.
by llama052 3y ago
Sadly for a lot of these companies it's more of a "business" decision than a technical one. Having said that I will not work for a company in the future that has their primary infrastructure in Azure.
73.
by llama052 3y ago
> Going into a "cloud native" stance and continuing to micromanage containers, VMs, databases, message buses, reverse proxies, etc. seems absolutely ridiculous to me. Honestly you're just paying the cloud provider to manag
74.
by llama052 3y ago
We use a few operators currently. - Prometheus operator Lets us spin up a prometheus monitoring stack on our kubernetes cluster for monitoring metrics and scraping metrics from our services pretty much automatically. - Thanos Operator Spins
75.
by llama052 3y ago
Honestly with a github action and Argo CD workflow the kubernetes patterns aren't that scary. However maybe I'm just too comfortable in the ecosystem at this point. I will say Kubernetes being as open as it is and all the overlapp
76.
by llama052 3y ago
If you can grasp the layers of abstraction it's a really really fast way to ship operational solutions. Yaml aside it's great for smaller teams and empowers them to do a lot more than they could traditionally do.
77.
by llama052 3y ago
Oh man, Munin.. I had forgotten about that! We are currently running a databricks cluster and avoiding the static-ish ganglia screenshots and injecting prometheus exporters to get data into grafana. Honestly wish the entire data space was m
78.
by llama052 3y ago
I'd still argue that it's easier to scale Pulling than it is a distributed push. It's kind of why prometheus went that route in the first place. Back in the days of puppet or nagios, which would take requests and not pull. It
79.
by llama052 3y ago
> Pulling metrics from your service is easy and simple. Pulling metrics from thousands and thousands of services, spread out over many clouds/regions/environments, puts a HUGE strain on the single pulling server. Especially if
80.
by llama052 3y ago
What are you missing specifically that New Relic has? We are a full grafana prometheus shop and the New Relic/Datadog price tag is insanity compared to the utilization we get out of the free tooling. Once you get over the learning curv
81.
by llama052 3y ago
> On the open source side Grafana and its stack (tempo, loki and prometheus) all just suck, they kinda scale and check all the boxes, but in a really stupid way (data nodes should probably be query nodes, rather than moving everything fr
82.
by llama052 3y ago
Honestly we've had great luck with HA prometheus instances shipping data to Thanos. All in kubernetes so we get to use pre-built operators. We don't really have to touch it other than updates. We are a 3 man team and we are holdin
83.
by llama052 3y ago
> Let’s be clear: if an environment can’t be created/deleted with a single command, and normal changes to its configuration (ex: size) can’t be applied in a simple way, you are not doing Devops. You are a sysadmin and you are living
84.
by llama052 3y ago
I'm willing to bet they are moving from databricks offerings, considering their pricing is insanity.
85.
by llama052 3y ago
Oh I see the operator now, looks decent. Before the deployment documentation I had found was very manual and full of a lot of pod exec commands. Worked with many operators in the wild and anything that gives you more control through CRD&#x2
86.
by llama052 3y ago
We really wanted to try redpanda, but operationally it does not appear to be very k8s* native and infact looks like a lot of one off hand holding to get it working properly. Hopefully that can get ironed out in the future. Until then we wil
87.
by llama052 3y ago
I wonder if they are migrating most of their platform to Azure.
88.
by llama052 4y ago
I don't understand how having k8s means you need significantly more people. It's just concepts put into a strict system. Now you're just shimming the same concepts with less supported hacks. Now you have to train your team on
89.
by llama052 4y ago
Completely agreed with this. K8s is not that operationally hard. The concepts are all there and it's just giving you a framework for it essentially. Many k8s operators out there to help you self host it. Abandoning the entire concept i
90.
by llama052 4y ago
Feels good to see them land on the same technical decisions my team and I have made. Some crazy progress from clickhouse!

More ›