The Data-Aware Kubernetes IDE. ⎈ ☸️ Multi-Cluster Groups 🗄️ Standalone & in-cluster Redis/Valkey 🐳 Local container playground 🛠️ Debugging toolkit Official

Joined October 2025
Keyscope retweeted
🚀 Kustomize: Customize Kubernetes without templates! Managing different configurations for Dev, Staging & Production? You don't need to maintain separate YAML files for everything. Kustomize lets you reuse base manifests and customize them with overlays. Here's what every Kubernetes engineer should know 👇 🔹 Bases vs Overlays 🔹 "kustomization.yaml" 🔹 Patches: Strategic Merge & JSON 6902 🔹 ConfigMap & Secret Generators 🔹 Image, Namespace & Label Transformations 🔹 Essential "kubectl kustomize" commands 🔹 Kustomize vs Helm 💡 Pro tip: Use "kubectl diff -k ./overlays/prod" to preview changes before applying them. 📌 Remember: - Kustomize → Customize existing Kubernetes manifests. - Helm → Package, template, and manage application releases. Save this cheat sheet for your next Kubernetes deployment! #Kubernetes #Kustomize #DevOps #SRE #GitOps
6
30
816
Last Week in Kubernetes Development: Week Ending October 18, 2026 - lwkd.info/2026/20261022
1
1
17
9,606
Released `built_collection 6.0.0`: pub.dev/packages/built_colle… It's a bug fix: `asList` and `asMap` now return unmodifiable views, as was always intended, instead of copying. It was intended because it was supposed to be fast. It's breaking if you rely on them returning the exact native `List` and `Map` types, hence the major version bump, but it should break almost nobody. Also added: `ListBuilder.of`, `SetBuilder.of`.
1
3
31
1,052
Keyscope retweeted
Flutter 3.47.8 (stable) & 3.50.0-0.2.pre (beta) are now live. This critical release addresses the eMudhra CA key compromise. If you target Android, Windows, or Linux, run flutter upgrade and rebuild your apps to protect users from potential TLS spoofing. goo.gle/4yDkt0U
14
138
32
570
75,324
Keyscope retweeted
Recently faced this question in a DevOps interview: 🟢 How does PVC work in Kubernetes ? 👉 A Pod doesn’t request a disk directly. It uses a PVC (PersistentVolumeClaim) to request storage. 👉 Kubernetes binds the PVC to an existing PV or dynamically provisions storage through a StorageClass. 👉 In AWS EKS, the storage is usually backed by Amazon EBS or EFS, allowing your application to retain data even when a Pod restarts.
8
9
61
1,520
--- - Kubernetes uses YAML - Helm uses YAML - Istio uses YAML - ArgoCD uses YAML - Backstage uses YAML - Ansible uses YAML - GitHub Action uses YAML - Gitlab CI uses YAML - Azure DevOps uses YAML - GCP cloud build uses YAML Get good at YAML
10
17
2
185
6,269
🔐Gateway API - Step 9: HTTPS, TLS & Security Production traffic needs more than routing. ✅HTTPS listener ✅TLS certificate ✅Correct certificate references ✅Least-privilege access ✅Secure configuration A working route is good. A secure route is better. #Kubernetes #Security #AWS
4
8
44
703
🚨 Before you upgrade to Kubernetes 1.37, check these 4 things. One of them will break something. Upgrades don't fail because of new features. They fail because of what got removed. 1. Static Pods can no longer read Secrets or ConfigMaps If any of your static pods (control-plane components, node agents) reference them, they'll break. Move that config into the static pod manifest. 2. cgroup v1 nodes failCgroupV1 has defaulted to true since v1.35, so the kubelet refuses to start on cgroup v1 unless you override it. Still on old AMIs? Find out before the upgrade window, not during it. 3. kube-proxy ipvs mode is on its way out Disabled by default around v1.40, removal planned for v1.43. If you run ipvs, plan the move to nftables now. 4. kubectl run -f is deprecated Use kubectl apply -f. This one will hit your old scripts and CI jobs quietly. The real lesson isn't in the release notes. Nobody gets paged for a deprecation. They get paged when a deprecation becomes a removal and nobody noticed. Do you have a pre-upgrade checklist, or do you find out in production? 🔁 Save this before your next cluster upgrade. 🚀 And if you want to learn production engineering directly with me: outages, Kubernetes failures, on-call, debugging and infrastructure decision-making: 🔗 Fill this form: tally.so/r/jaKrXQ My team will reach out if you're a fit.
3
9
1
37
1,303
Keyscope retweeted
Real-time data is only an advantage if agents can use it. Redis Context Retriever makes that possible. Schedule time with a Redis expert to see it in action: redis.io/context-retriever/
3
2
4
708
DocumentDB 1.0 is now generally available. An MIT-licensed, MongoDB-compatible document database built on PostgreSQL, DocumentDB lets you run existing MongoDB workloads on a familiar Postgres foundation. Find more details on the 1.0 GA release here: documentdb.io/blogs/posts/do…
4
58
5
335
28,596
Keyscope retweeted
🚀 Kubernetes Helm — the cheat sheet every DevOps engineer needs! Managing Kubernetes deployments manually can get messy. Helm makes it easier to package, configure, version, and deploy applications using reusable Charts. Here's what every Kubernetes engineer should know 👇 🔹 Charts & Releases 🔹 "Chart.yaml" vs "values.yaml" 🔹 Helm templates 🔹 Essential Helm commands 🔹 Install, upgrade & rollback 🔹 Managing dev, staging & prod environments 💡 Pro tip: Master "helm upgrade" and "helm rollback" before managing production deployments. Save this cheat sheet for your next Kubernetes project! 🔖 #Kubernetes #Helm #DevOps #SRE #CloudNative
2
13
70
2,286
Many people on X are going to get offended by this 😅 These days I keep seeing posts like: “AI can write Terraform code.” “AI can write Kubernetes manifests.” “AI can write Dockerfiles.” “AI can automate coding.” And then people say: “Now you need to learn deep networking.” “Troubleshooting is more important than ever.” “Just use AI, you don’t need to know everything.” My friend… start somewhere. If you’re new to DevOps or any technical field, PLEASE learn your basics. Don’t directly jump into Kubernetes, copy a manifest from Claude, apply it and think you know Kubernetes. Eventually, you’ll get fucked when something breaks. Use AI as a companion, not as a copy-pasting machine. If AI generates a Kubernetes manifest, understand what it generated. If AI writes Terraform, understand what resources it is creating and why. If AI gives you a Dockerfile, understand what is happening inside the image. Learn the important tools. Learn networking. Learn Linux. Learn troubleshooting. Learn how systems actually work under the hood. And yes, use AI. Of course. The interesting part is that I still see people saying: “AI will do everything. You don’t need to learn these things anymore.” Really? Then who is going to optimise that Terraform code according to your actual context? Who is going to debug the Dockerfile when the build suddenly breaks? Who is going to understand why your Kubernetes workload keeps crashing? Who is going to make the decision when you get paged at 3 AM? Who is going to decide whether the AI-generated solution is actually safe to deploy? If AI can do all of this without technical understanding, why don’t companies just hire a 10–15 year old kid, give them Claude Max and let them run production? Because that’s not how engineering works. AI can generate code. But understanding the problem, providing the right context, validating the output, debugging failures and making the final decision still requires engineering knowledge. And honestly, I don’t think people should blindly believe everything they see on X. Not even me. Keep learning. Use AI. Go deeper as your experience grows. But don’t skip the fundamentals just because AI can generate the syntax for you. You still need to understand what you’re building.
3
13
660
It's been one hell of a week in my local homelab where I experiment, break things, troubleshoot, and learn about Kubernetes, cloud, and DevOps. Over the last few days I completed: ✅ ArgoCD with Image Updater ✅ Cosign keyless signing ✅ Dynamic GitHub Actions matrix ✅ Prometheus + Grafana monitoring ✅ Centralized logging using the EFK stack One thing I realized is that building something from scratch teaches you way more than following a tutorial. Some things I learned that weren't covered in most beginner tutorials: Using the App of Apps pattern in ArgoCD Managing deployments with Helm charts (both my applications and the EFK stack) Understanding how all the components actually work together instead of just deploying manifests I didn't end up using Fluent Bit Lua scripts because my use case didn't require them. Most of my time wasn't spent writing YAML—it was spent troubleshooting. Debugging why something doesn't work teaches far more than watching another "Deploy EFK in 10 minutes" video. The homelab is slowly starting to look like a production-grade platform, and there's still a lot more to build. 🚀
5
2
27
778
Keyscope retweeted
Flutter 3.50.0-0.1.pre Beta is live! Highlights: 💙 Hybrid Composition++ enabled by default on Android for smoother platform views 💙 Impeller update: Purges offscreen render target cache during low-memory pressure ...& more. Explore the changelog →goo.gle/4e7sBPO
12
16
3
249
24,460
Keyscope retweeted
A model trained before Redis 8 will still give you the old defaults with total confidence. The Redis Docs MCP lets your agent read the current docs instead. You can connect it and read how we built it and what we measured here: redis.io/blog/how-we-built-t…
4
4
1
26
1,720
Keyscope retweeted
Introducing the official Appwrite Helm chart for Kubernetes 🚀 You can now deploy self-hosted Appwrite on your Kubernetes cluster with support for managed databases, Functions, Sites, and more. Get started: appwrite.io/blog/post/announ…
20
4
1
45
2,312