Oded Nahum

TMMi IN THE DEVOPS WORLD UPDATE AVAILABLE The DevOps working party of the TMMi Foundation, chaired by Erik van Veenendaal, has released an updated version of the document "TMMi in the DevOps world". Now including the interpretation for TMMi level 3. Learn what TMMi means and how to apply it in a DevOps context. https://lnkd.in/euc2TgSV https://lnkd.in/enxVUSdj Suresh Chandra Bose G, PMP Szilard Szell Katalin Balla Kari Kakkonen Rik Marselis Mattijs Kemmink TMMi Foundation ISTQB® - International Software Testing Qualifications Board

30

4 commentaren

🚀 VMware → OpenShift Virtualization: Lessons from the Field We’re currently helping a large bank migrate workloads from a massive VMware environment to OpenShift Virtualization and it’s been an eye-opener. There’s no doubt VMware has been the gold standard for virtualization for decades rock-solid hypervisor, mature tooling, and deep enterprise roots. But after the Broadcom acquisition, the narrative has shifted. Licensing, uncertainty, and long-term roadmap questions are pushing many to explore alternatives built on open technologies. So far, here’s what we’ve learned: ✅ The biggest challenge isn’t technical it’s mindset. Teams are used to managing VMs like static pets; moving to Kubernetes-native virtualization means treating them like cattle, integrated into pipelines, GitOps, and policies. ✅ Storage and networking design matter more than ever you can’t just “lift and shift.” We’ve seen how tuning ODF (OpenShift Data Foundation) and leveraging proper network attachment definitions for isolation make or break performance. ✅ Observability and Day-2 operations must evolve; operators, monitoring, and automation now need to handle both VMs and containers side by side. The transition isn’t trivial, but it’s rewarding we’re helping this bank move towards a future where containers and VMs coexist seamlessly, managed through one Kubernetes control plane. 💬 If your organization is also evaluating a new home beyond VMware, reach out we’d be happy to share our learnings and help you plan the journey. 🔖 #OpenShift #Kubernetes #Virtualization #StakaterCloud #PlatformEngineering #VMware #CNV #Migration #GitOps

261

43 commentaren

Curious about the difference between the HashiCorp Vault Secrets Operator and the Vault Agent Injector? How do you integrate Vault with your Kubernetes workloads? 🤔 Check out this article to find out the key differences --> https://lnkd.in/eB-GbTCz

33

4 commentaren

OpenShift vs. Vanilla Kubernetes: A Strategic Perspective for Enterprise Architects In the rapidly evolving world of cloud-native technologies, Kubernetes has undeniably emerged as the de facto standard for container orchestration. As solution architects, the challenge lies not just in adopting Kubernetes but in choosing the right flavor that aligns with business goals, operational maturity, and security needs. This is where the strategic value of OpenShift versus vanilla Kubernetes becomes crucial. At its core, Kubernetes provides a powerful, open-source foundation for container orchestration. It automates deployment, scaling, and management of containerized applications—an invaluable capability for modern, agile enterprises. However, Kubernetes by itself is just a building block—it offers the essentials but leaves much to be manually integrated. Beyond the core, organizations often face a complex landscape of tooling, security policies, CI/CD pipelines, and platform management solutions. This can stretch expertise and delay time to market. This is where OpenShift, Red Hat’s enterprise container platform built on Kubernetes, unlocks significant value for solution architects and their enterprises. OpenShift enhances Kubernetes with a comprehensive suite of tools designed to simplify and accelerate enterprise adoption: Developer Productivity: Built-in CI/CD pipelines, a rich developer console, and seamless source-to-image workflows reduce friction and speed app delivery. Developers can focus on innovation rather than infrastructure. Security by Design: OpenShift enforces strict security policies out-of-the-box, such as running containers as non-root, integrated identity and access management, and compliance automation, allowing architects to build secure platforms confidently. Operational Efficiency: Automated upgrades, patch management, and multi-cloud deployment support reduce the operational burden. OpenShift’s tightly integrated ecosystem minimizes the manual glue work often required in vanilla Kubernetes deployments. Enterprise Support & Ecosystem: Backed by Red Hat’s enterprise-grade support and a robust ecosystem of certified partners, OpenShift provides peace of mind for critical workloads. From a solution architect’s viewpoint, these differentiators translate into faster deployment cycles, higher security posture, and reduced Total Cost of Ownership (TCO). While vanilla Kubernetes offers unmatched flexibility and control, it demands extensive expertise and additional integrations. OpenShift, conversely, provides a curated, enterprise-hardened experience that accelerates cloud-native transformation without compromising on control or openness.

38

1 commentaar