Juliet Salinas

🚦 Tired of "green" dashboards while users hit issues? Meet Canary Checker: true Kubernetes-native health validation! It goes beyond basic probes to check your workflows, APIs, and dependencies—before real customers do. Boost reliability, cut downtime, and monitor what actually matters! #Kubernetes #DevOps #Observability https://bit.ly/47AEM5f

8

🚨 One of Kubernetes’ most widely used components is being retired. And it’s not because of a shiny new replacement. In our latest episode, I sat down with Kat Cosgrove, elected member of the Kubernetes Steering Committee, to unpack the decision to retire Ingress NGINX. This wasn’t a roadmap tweak. It was a hard call driven by realities many platform teams quietly face: ⚠️ Escalating security risk 🧱 Mounting technical debt 🔥 Maintainer burnout at scale We get into: - Why there is no true drop-in replacement for Ingress NGINX - What migration really looks like (spoiler: it’s not just “switch to Gateway API”) - What this decision reveals about Kubernetes governance and the responsibility of protecting critical open-source infrastructure - Why “keeping it alive” is sometimes the riskier option If you run platforms, depend on Kubernetes, or care about the sustainability of open source, this conversation is required listening. 👉 Listen to the full episode: https://lnkd.in/em37Pa8K 👉 Share it with your platform team 👉 And ask yourself: what technical debt are we normalizing today? #Kubernetes #PlatformEngineering #OpenSource #DevOps #Ingress #NGINX #CloudNative #GatewayAPI #Leadership #DeveloperAdvocacy

1

Octopus Deploy has a few “oh wow, I didn’t know that existed” features. We pulled together some of our favorite hidden gems, from the Kubernetes Agent and resilient Tentacle communications to OctoTerra, API examples, and handy YAML & GitHub Actions generators. Whether you’re deep into IaC or just getting started, there’s probably something here that makes your life easier. Take a quick look in Robert's blog post👇 https://lnkd.in/g9V9J7BA And if we missed your favorite feature, tell us 👀 #OctopusDeploy #PlatformEngineering #DevOps #Automation

14

In Kubernetes v1.35, spec.jobControllerManagedBy hits GA. That means full handoff of Job reconciliation to external controllers is now official. It unlocks tricks like MultiKueue, where a single management cluster fires off Jobs to multiple worker clusters, without losing sight of what’s running where. Big shift: Kubernetes steps back from owning the whole Job lifecycle. Scheduling and execution are finally split, clearing the way for smarter, more modular batch systems. https://lnkd.in/g3zGaTvQ --- Like this? Subscribe 👉 https://faun.dev/join

1

ICYMI: Kubernetes v1.33 brought some big updates. From beta support for in-place pod resizing to API graduations and stability enhancements, this release is packed with features that matter to teams running Kubernetes in production. Learn More: https://ibm.co/4kBzl9Y #Kubernetes #DevOps #CloudNative #CNCF

6

Running control planes inside Kubernetes instead of on static VMs changes how platform teams operate. Clusters can be managed like applications with GitOps tooling such as ArgoCD or Flux, while gaining the built-in benefits of autoscaling and self-healing. In v0.27, we introduced Private Nodes, giving each virtual cluster dedicated worker nodes for stronger isolation and no host-cluster syncing. With v0.28, we’re taking the next step with Auto Nodes. This automates how private nodes are provisioned and scaled, removing manual steps and enabling just-in-time elasticity across environments. 👉 Explore the Future of Kubernetes Tenancy Launch Series: vcluster.com/launch #Kubernetes #vCluster #MultiTenancy #CloudNative

6

1 Comment

Dan Mattox, Senior Director of Engineering @ Exostellar, explains how Dynamic Resource Allocation (DRA) in Kubernetes 1.32 represents a fundamental shift in managing specialized hardware like GPUs. He discusses how DRA transforms GPUs from bolt-on additions into first-class citizens within Kubernetes, eliminating the need for provider-specific device plugins that previously required extensive customization from chip manufacturers. Watch the full interview: https://ku.bz/5ymZxdYXq This interview is a reaction to John's episode https://ku.bz/wP6bTlrFs

2

Your Kubernetes. Ready on Day One. Kubernetes isn’t hard because it’s Kubernetes. It’s hard because teams DIY it into production. Obmondo delivers clusters that are: ▪️ GitOps-native ▪️ Secure by default ▪️ Fully monitored and backed up ▪️ Automated from Day 1 to Day 2 No weekend-long rollbacks. No hidden vendor agenda. Just Kubernetes that runs — without the chaos. #Kubernetes #Day2Ops #CloudNative #GitOps #PlatformEngineering #LinuxAdmin #CyberSecurity #UptimeMatters

5

DEMYSTIFYING KUBERNETES: Chapter 3 You’ve mastered VMware’s SDDC stack. Now see how it all maps to Kubernetes. Chapter 3 of our "Demystifying Kubernetes for the VMware Admin" series walks through VMware Cloud Foundation layer by layer, showing the Kubernetes equivalent for each component—so you can move to cloud native with confidence, not guesswork. Read: “Mapping the Stack: SDDC to Cloud Native” https://lnkd.in/gtnjkyz9 #Kubernetes #CloudNative #BroadcomEscapeStrategy #Portworx

44

1 Comment

🛠 Your Terraform setup shouldn’t feel like a ticking time bomb. But if it keeps breaking in production, chances are you’re making one (or all) of these mistakes: 🚫 Shared or mismanaged state files 🚫 Poorly structured modules 🚫 No CI/CD or change validation At Puffersoft, we’ve seen it all — and we fix it all. 💡 Get a FREE Terraform Audit and let’s make your infra future-proof. www.puffersoft.com #Terraform #IaC #DevOps #CloudEngineering #AWS #Azure #PufferSoft #InfraAsCode #TerraformAudit #CloudOps #InfraFix

9

Are your Kubernetes Network Policies enough? 💭 Default Kubernetes policies work, until you need real security and visibility. Calico takes it further with cluster-wide policies, DNS-based controls, encryption, and deep observability through eBPF and WireGuard. If you’re running Kubernetes in production, this article shows how Calico helps you move from basic traffic rules to a comprehensive security model. 👉 Read more: https://lnkd.in/e7Y3QdpD #Kubernetes #Calico #NetworkSecurity #CloudNative #DevOps #NetRomSoftware #SoftwareDevelopment

19

Infrastructure as Code with Terraform: Automating Infrastructure Provisioning Automate your infrastructure provisioning with Terraform. Deploy resources consistently and reduce manual errors. In today's fast-paced cloud environment, managing infrastructure manually is no longer sustainable. It leads to inconsistencies, operational bottlenecks, and increased risk of human error. This is where Infrastructure as Code (IaC) truly shines, and Terraform stands out as a leading solution for bringing engineering principles to infrastructure management. ✅ Why IaC with Terraform? 1️⃣ Consistency & Repeatability: Define your infrastructure declaratively. Terraform ensures that your environments (development, staging, production) are identical, eliminating configuration drift and "it works on my machine" issues. 2️⃣ Speed & Agility: Spin up entire environments in minutes, not hours or days. This accelerates development cycles, enables rapid prototyping, and supports continuous integration/delivery (CI/CD) pipelines. 3️⃣ Reduced Operational Overhead: Automate the repetitive, error-prone tasks of provisioning and managing infrastructure. This frees up engineers to focus on higher-value work, innovation, and solving complex challenges. 4️⃣ Version Control & Collaboration: Treat your infrastructure like application code. Store Terraform configurations in Git, enabling versioning, peer review, and a clear audit trail of all infrastructure changes. This fosters better team collaboration and accountability. 5️⃣ Scalability & Cost Efficiency: Design infrastructure that scales dynamically to meet demand, preventing over-provisioning and optimizing cloud spend. Terraform helps manage resources efficiently across multiple cloud providers. Terraform's declarative approach allows you to define the *desired state* of your infrastructure, and it intelligently figures out how to get there. This abstraction simplifies complex cloud operations, making it accessible for teams to manage infrastructure at scale, reliably, and securely. Adopting IaC with Terraform is not just an operational improvement; it's a fundamental shift towards more robust, agile, and developer-centric infrastructure management. #DevOps #IaC #Terraform #CloudAutomation #InfrastructureAsCode #SiteReliabilityEngineering #CloudComputing

1

Keeping up with releases across Kubernetes, observability, CI/CD, and developer tools is brutal for modern teams. You know the drill: Kubernetes 1.35 drops. Grafana ships breaking changes. Your Prometheus setup needs patching. Each requires digging through changelogs, assessing impact, and manually updating dependencies. relnx.io changes this. It's a release intelligence and automation platform that tracks your stack, highlights what matters (features, security fixes, breaking changes), and automatically opens PRs to keep everything current. Here's the workflow: → New version ships (K8s, OTel, Grafana, whatever you use) → relnx creates a PR with the upgrade → Breaking changes and impact analysis appear right in the PR description → Your team reviews with full context and merges confidently The outcome: - Safer upgrades backed by clear intelligence - Fewer production surprises - Teams stay current without the manual changelog grind Stop reacting to outdated dependencies. Start automating your upgrade pipeline. 👉 Join relnx now: https://www.relnx.io/

2

Ever handed your developers a “best-practice” Terraform module only to discover three forks later that none of them enabled backups and you’re left scrambling to fix production?  You’re not alone. In our latest blog post by Jake Klein, we dive into why shipping raw Terraform modules often leads to sprawl, misconfigurations, and manual patching nightmares across teams. But what if you could wrap those same reusable modules in a self-service platform layer enforcing compliance, automating updates, and giving developers a familiar API without exposing them to Terraform’s complexity? Enter Kratix Promises: the open-source framework that lets you bootstrap existing Terraform modules into managed, API-driven services with a simple CLI command. Discover how Syntasso Kratix Enterprise seamlessly integrates with Backstage, GitHub Actions, and Jira to deliver approvals, governance, and fleet-wide updates, no refactors required. Ready to transform your Terraform workflows and empower your teams? 👉 Read the full story and get started with our guided Quickstart: https://lnkd.in/dMjNuYTN #Syntasso #Terraform #InfrastructureAsCode #InternalDeveloperPlatform #Kratix

3

This article explains how Kubernetes 1.35 enables in-place Pod resizing without restarts, covering the technical implementation from cgroup v2 mechanics to production challenges. More: https://ku.bz/rVc2f95jW

47

Kube-bench checks compliance. Kube hunter checks if you are actually secure. Kubernetes clusters can accidentally expose things like the API server, etcd, or weak RBAC permissions without teams realizing it. Kube-hunter helps find these issues by acting like a real attacker and probing your cluster for weaknesses. Instead of just reviewing configs, it actively tests what an attacker could actually access or exploit. It can run: - Externally (like an outsider), - Inside the cluster (as a pod), or - Scan the network to discover exposed services. This makes it useful for catching real risks like open dashboards, public API endpoints, or insecure etcd access. Tools like kube-bench and Trivy mostly check configurations and known vulnerabilities. Kube-hunter is different because it simulates real attack paths, not just compliance checks. That’s why teams often use it in pre-production to catch practical security gaps before going live. 𝗚𝗶𝘁𝗵𝘂𝗯: https://lnkd.in/g6arFvPT #devops #devopstools

55

1 Comment