Kubernetes

“The devops department at my company, which has around 500 services across a load of kubernetes clusters / regions”

“I have instantiated so many K8s Ingress that were nginx”

“I personally (1) run them in k8s (2) replace my harness builtin tools”

“We run a several hundred k8s VMs orchestrated by Rancher”

“At my company we run Kubernetes workloads where we have 20-30 or sometimes more pods connecting to a single Postgres instance”

“fits natively within our k8s env.”

“we generally see tech adopting initially due to the technical deployment required (e.g. k8s)”

“Since the issue was due to the intersection of k8s and effect, I don't think reading a bunch of docs would have really helped.”

“It's trivial to switch clouds now with K8 stack and Claude Code.”

“the source of most of the problems I've seen with infrastructures using Kubernetes came from exactly this kind of approach.”

“At $WORK we've been using the Zalando Postgres kubernetes operator”

“I live off the learning I did in Linux now that I administer Kubernetes clusters for a living.”

“At work, we generate a couple thousand lines of k8s YAML from ~0.1x of that in CUE.”

“we run our services in k8s cluster. In staging env we maintain a REPL connection”

“When I update the Kubernetes or Talos version new nodes will be created”

“we are already running our own k8s clusters in our datacenters”

“we've run it on Kubernetes for 6 years.”

“it was meant to handle 10k+ VMs (and a lot of other resources, multiple k8s clusters)”

“I bought three of them for a Kubernetes cluster and it seems to work great for a few days and then constant black screens”

“Auto-scaled Kubernetes deployments, one for each availability zone”

“We have Kubernetes cluster with all DNS Updating, Cert Grabbing and Prometheus monitoring so we run static sites from nginx container.”

“We run on-prem k8s and do the pip install stage in a 2CPU/4GB Gitlab runner”

“That isn't present at all in prod, or when running in k8s or docker compose locally.”

“thousands of concurrent app deployments on shared Kubernetes clusters”

“Right now I'm leading a Kubernetes + AI implementation.”

“So a K8s namespace named test02, another named test-featurebranch, and another named staging-featurebranch”

“watches (via client-go informers with client-side caching) to sync data into a Postgres database as JSONB... Kubernetes events”

“I do understand I am privileged by having grown with the technology ... and now in k8s etc.”

“We've been using Hetzner's dedicated servers to provide Kubernetes clusters to our clients for a few years now.”

“We're running standard Prometheus on Kubernetes (14 onprem Talos clusters, total of 191 nodes”

“we run prod on a cluster, staging on another one, then it's tooling clusters like dev spaces, ML, etc.”

“This is how we run our simulators and analytics within the same k8s cluster.”

“The runtime was k8s.”

“once we switched to Kubernetes we used a deamomset & host tagging (taints?) to pull a variety of thingies to each host”

“Then we ran Kubernetes on a cloud node because it was hard to manage the workloads.”

“we run K8s + containers in some shape or form (as well as in... basically all previous jobs)”

“the self hosted runners were hosted on K8s using Arc”

“we can focus on your app not the cluster setup.”

“We migrated microservices from Heroku to Porter, and also from standalone VMs and K8s running on AWS to Porter.”

“We have several ASP.Net Services that hosted 100% on Kubernetes”

“We have a pretty cool tech stack... We have a kubernetes cluster that has Agones for game server orchestration”

“So we added some magic kubernetes sauce and voilà, you got the cloud decompiler”

“I've even seen people ssh into running containers and change things.”

“We switched to Pkl for our Kubernetes resource generation”

“My team has been developing against a fully remote environment (K8s cluster) for some years now”

“we have to run a significant number of Kubernetes pods to serve this workload.”

“with the on-prem system where we run our own massive k8s/vm/data lake cloud, every team just throws things at it”

“I use this in production in large corporate projects on k8s.”

“This is currently a long lived service that runs as a deployment alongside a bunch of ephemeral runners”

“At work at my new job we run mixed workloads in k8s and I don't really see a problem”

“We run these on Kafka or rest api. We even runs jobs and corn jobs in k8s.”

“we also shared an article about how we run these indexing jobs at scale at deepset with kubernetes, SQS, s3 and KEDA.”

“I never ran postgres in prod in k8s, but i used cloudnative-pg for some light, non-critical loads, dev/stg stuff.”

“Our k8s cluster was on EKS and it worked out very well.”

“We switched over to kubevirt[0] (essentially qemu/kvm inside a kube cluster) to handle our CI”

“We ditched Prometheus in favour of Statsd before moving to Kubernetes.”

“now we just use or pipeline to prepare pods and push it to k8s, continuous deployment”

“One behavior we observed is it crashes consistently in k8s.”

“At my work, we use environment variables all the time for configurations, e.g. for telling a kubernetes pod where to find the database.”

“we switched to our own hosted-on-k8s GitLab summer 2019 and it's been rock solid since.”

“I have a Kubernetes cluster in hetzner with split horizon DNS”

“the entire cluster and all communications inside the cluster/between pods is IPv6 only.”

“We run our own runners, on a nodegroup in k8s, which downsizes after the runners go idle”

“We run a lot of services in Kubernetes, some of those services also run background jobs”

“We actually used outside contractors (actual k8s gurus) to do the work.”

“we still don't know or really need to know a ton about k8s, but we are familiar with some basics around pod sizing”

“we run kubernetes on multiple VPS providers, including public clouds”

“we're now on dotnet 6 and kubernetes in azure”

“We switched some of our stack from k8s and swarm to Fargate, and API Gateway (Lambda).”

“We tried moving to k8s but found the current setup simpler.”

“ClusterAPI has been the way my company has been doing things lately and I can honestly tell you it's been transformative.”

“we switched from self-managed k8s on EC2 to Fargate. Took about 2 months part-time with some consultants to get thing squared away.”

“Load was very predictable, and ran on k8s anyway.”

“mostly for cost efficiency (and adoption of k8s for even better cost)”

“We made the switch in our EKS and vanilla k8s clusters in 2021.”

“We've switched everything other than our K8s cluster and local Mac dev away from it”

“we migrated for our k8s stuff from AWS to self-manged Hetzner Cloud and save roughly 66%”

“We wrote about how we migrated off Cloud Run to K8s”

“Code is mostly on github now, we have peer reviews, deploy to kubernetes.”

“We use kubernetes, ssd optimizations for fast embedding retrieval, and custom compiled TensorFlow container images.”

“Just to name the ones we use at Helsinki City.”

“we run notebooks on the Kubernetes clusters (AWS' EKS, GCP's GKE, Azure's AKS, or DigitalOcean) of the users”

“We use CityNetwork public cloud managed services (MongoDB, Rancher/Kubernetes and Openstack for edge network/load balancer)”

“and Kubernetes clusters, and any other piece of infrastructure that becomes critical to your business”

“then you have two problems: K8s and helm problems to solve”

“our prod system is hybrid with our own data centers running k8s”

“I deployed CouchDB in a Kubernetes cluster (not with HA as I didn't have high availability requirements)”

“We run a few kubernetes clusters on premise, and for the longest time it was just 1 person running some Kubernetes clusters”

“Turn on the VPN to access a k8s cluster.”

“What we run in the Cloud today is the OSS version on k8s.”

“it can auto deploy to our k8s staging cluster (though it worked similar when it deployed to vms).”

“We were on kubernetes. Except we weren't allowed to use k8s.”

“we are actually able to just throw away our k8s cluster and it will be recreated from scratch.”

“we run k8s on bare hardware”

“We run on a managed Kubernetes provider called Coreweave Cloud”

“in the end we moved to Kubernetes anyways.”

“We partially resolve this by having different namespaces in each of our environments. Nothing is ever run in the 'default' namespace.”

“dd was ridiculously expensive and resource hungry in kubernetes environment”

“k3s is actually pretty simple to use now.”

“we're using all the modern cloud tooling: Spring Boot, Azure, containers, K8S, Gitlab pipelines.”

“we switched to digitalocean once they had managed kubernetes. It's such a pleasure to not have to worry about it”

“we use kubernetes heavily and our development environment matches production about as closely as possible for the architecture we have.”

“daily operations within our k8s clusters for example”

“We've tried k8s several times and have always ended up going back because we didn't need the complexity.”

“We use it for containers to be run on k8s.”

“I'm using Docker on Mac for Kubernetes "application" development.”

“No, we use Kubernetes, grpc and protobuf as base, Prometheus and Grafana for monitoring.”

“I do this for my k8s cluster hosted by a bunch of pi's.”

“also learned a lot from running Kubernetes in production at my full-time job”

“We run about 10 Kubernetes clusters, and each cluster comes with our company's 'kernel'.”

“we can happily set "always" as imagePullPolicy in our kubernetes clusters.”

“I've also used k8s extensively and nomad/consul is more 'open' and less opinionated.”

“We migrated to on-prem GitLab running on k8s via the official Helm chart a year ago.”

“it would cost us many multiples in the cloud (excluding our TURN relays which aren't k8s)”

“At work we run a handful of distributed clusters, if anyone does an equivalent of sshing into a box and poking around (in our case, `kubectl exec`)”

“We're now running a multi-node on-premises kubernetes cluster”

“we also had alerts for our k8s nodes not getting ready (calico images)”

“Not understanding how k8s work, or actual provider screwing up?”

“it is harder to delete the k8s resources in all places when you delete a k8s configuration file.”

“I worked at a company that wrote an internal infrastructure/deploy management tool based on Kubernetes.”

“There was lot of memory leak when used as the storage for prometheus for our kubernetes cluster.”

“hundreds+ of hours of experience dealing with it in production”

“Hosted on GCP kubernetes, using 0.25 cpu and 250 mem”

“1-2 years ago when Kubernetes was new I tried it, and somehow got it to build”

“Yes, I was talking about deploying to our existing cluster. ... Ironically, it's often harder to deploy applications that offer their own k8s deployment approaches”

“We train models as kubernetes cronjobs defined by a minimal properties file per model”

“same CICD process with docker container deploys little web server onto our Kubernetes environment.”

“Since we run on Kubernetes, rolling back the code is a matter of redeploying the older images.”

“We run s3 (minio rook ceph on k8s) locally so the network latency is a cluster latency.”

“I never used helm / kubernetes before 3 months ago.”

“We run the infrastructure in the cloud (we run it on GCP using Postgres and k8s”

“in the early days of k8s, I was hacking through the alpha-stage ingress plugin and editing haproxy configs by hand anyway”

“Running Elasticsearch on K8s storing 16TB of compressed logs”

“We switched our staging/dev environments to DO because of cost. A small Kubernetes cluster and hosted Postgres does not cost much there”

“Consequently we switched to Kubernetes.”

“Databases that have huge IOPS requirements are still deployed outside of Kubernetes and run in i3 instances.”

“We run lots of multitenant kube clusters, and I would still recommend anyone who expects to grow to create hard walls between clusters”

“I've been using K8's for over a year and have built some golang apps.”

“I've played with them in the past, but not spent enough time with them to be confident using them in production.”

“Dabbled a bit with Docker and Kubernetes on Azure”

“I learned and brought in production the followings: Kubernetes”

“We initially targeted Kubernetes because that's what we use and packaging for it is simple.”

“All things that, in my opinion, a Kubernetes deploy tool should have.”

“For Kubernetes, we're using the schema at https://github.com/kubernetes/api”

“I am a bit weary about configuring things that run inside your Kubernetes cluster through amazon apis”

“We run on-prem k8s, on bare metal and VMs.”

“Currently, all of our k8s nodes with 16 cores are running with an average load 5-7.”

“We run our builds within containers (using the Jenkins k8s plugin) for repeatability”

“We are using a similar setup. K8s, Bazel, Go, Java (Android), Swift (iOS), Typescript.”

“You want docker to have proxy settings but not kubernetes. We use kubeadm and kubespray to install upstream.”

“these days it's more the Kubernetes definition”

“since we've moved to Kubernetes I'm hoping this can be automated almost entirely.”

“I've run vanilla k8s for about 3 years now in prod but am also fairly familiar”

“outputs a yaml manifest ready to kubectl apply.”

“we use gitlab to render and deploy a template as a normal k8s object.”

“Every repo contains a "deployment" directory with a dir each for "staging" and "production" with all of the Kubernetes manifests”

“each of our Kube clusters has a bastion VPN host that puts you inside the VPC and handles DNS to Route53”

“We run several hundred tasktiger workers in production (deployed using Kubernetes)”

“We run our apps on Kubernetes, where you'd naturally want to tune worker scheduling dynamically to accomodate queue size.”

“Setting the memory limit to 200mb is more than enough to prevent OOM kills in Kubernetes.”

“We currently run Kubernetes across all major cloud providers and we'd like some help.”

“We run it all on kubernetes.”

“We run Kubernetes with Debian 8.”

“We're slowly migrating our stack over to Kubernetes.”

“Every k8s service has a DNS label. We ensure that the DNS label can be derived from the username.”

“We're using packer to create images/docker and then distribute them automatically via kubernetes”

“to interact with Kubernetes and other internal services over a secure connection.”

“We evaluated it briefly and decided it was too limited and immature compared to Kubernetes.”

“Juenkins' Kubernetes plugin allows to mount secrets like with usual pods so we deploy test secrets just like we normally do production ones.”

“As a Kubernetes user who's been running 500+ containers in production for a little over a year now”

“we run in a buildroot based VM on your laptop so that we can run k8s components and a docker daemon cross platform”

“The DNS records for the internal records are done using the kubernetes middleware”

“Clocker can deploy a Kubernetes cluster with an HAProxy load-balanced set of masters and an auto-scalable cluster of workers”

“we honestly needed to stand up kubernetes on-premise and in public/private clouds.”

“In one year we migrated a full set of micro-services into a new infrastructure based on Kubernetes and Docker.”

“My company is too damn small to have a Kubernetes/Openshift Cluster/Machines running just idling”

“We run everything in kubernetes and Helm ensures we have consistent deployments of containers”

“we've replaced the Amazon control plane with a Kubernetes control plane”

“the model logic can be run within our optimized container based runtime built on Kubernetes.”

“We deployed K8S on AWS (I'm a dev at Appuri).”

“they can use elastalert (running in Kubernetes) to alert on events”

“I'm (probably) the primary maintainer of kube-up on AWS.”