Carlos Mestre del Pino

Embracing sustainability: managing Kubernetes clusters with innovation and responsibility In the Nederlandse Kubernetes Podcast, Maarten and Jurg shared how they use open-source components and the Cluster API to manage Kubernetes clusters efficiently. They leverage tools like KubeVirt to manage virtual machines, allowing them to run Kubernetes within Kubernetes and maximizing resource utilization and flexibility. A key strategy was using refurbished hardware. By extending the lifespan of existing hardware and integrating it into its infrastructure, Aknostic reduces costs and minimizes environmental impact. This approach aligns with its commitment to sustainability, proving that high performance and sustainability practices can go hand in hand. The always-returning discussion with this topic is the alleged increased carbon efficiency of new model hardware (chips in particular). The point is that stuff's lifespan is essential. Refurbished can mean reusing the chassis and retrofitting it with later generations of chips, memory, and disks. However, this debate will ultimately be settled with full transparency (embodied emissions) and carbon reporting. 💡 In more everyday terms, perhaps old shit running the Nordics is better than the latest and greatest in a dense urban environment like Amsterdam. Share your thoughts on balancing IT infrastructure performance, cost, and sustainability. How do you integrate sustainability into your tech practices? #Sustainability #Kubernetes #OpenSourceInnovation

4

Running distributed load tests for #Kubernetes applications has limitations when it comes to resources and scalability. Unlike the #k6Operator, Testkube integrates natively with Kubernetes to make distributed load testing easy. Read about how it works https://lnkd.in/e9WV2uVp

5

🌍 Terragrunt: Why We Recommend It for Our Clients 🌍 Terragrunt (https://lnkd.in/dYc-NRJu) is an essential tool for anyone using infrastructure as code. It's a thin wrapper that provides extra tools for keeping your Terraform configurations DRY, working with multiple Terraform modules, and managing remote state. Here’s why we suggest using Terragrunt: Here’s why we suggest using Terragrunt: - Terragrunt allows you to reduce repetition in your Terraform code by promoting reusable components. - It simplifies the use of multiple Terraform modules, making your infrastructure code cleaner and more manageable. - Terragrunt makes managing remote state easier and more secure, reducing the risk of state file corruption. - Terragrunt supports both Terraform and OpenTofu. This support ensures that no matter your preference, you can benefit from the organizational and operational efficiencies that Terragrunt brings to the table. At Naviteq Ltd, we recommend Terragrunt to all our clients to enhance their infrastructure management, boost productivity, and ensure scalable and maintainable codebases. #Terragrunt #Terraform #OpenTofu #DevOps #InfrastructureAsCode #CloudComputing

7

Ready to take your MongoDB skills to the next level? 🔗 https://lnkd.in/ertdgNMS 🚀 Check out Diogo Recharte's deep dive demo on provisioning MongoDB clusters in Kubernetes! From setup to backup & recovery, learn how to master your database deployment with ease. Percona #Kubernetes #MongoDB #TechDemo #DatabaseManagement #Percona #CloudTech

6

🌐 Interfaces in Kubernetes: Why Standardization Matters If you're starting out with Kubernetes, you've probably encountered CRI, CNI, and CSI – but why are these interfaces essential? 🤔 Kubernetes was designed to work with diverse hardware and providers, but achieving consistency across them takes time and effort. Imagine switching cloud providers for your Nodes – without standardization, every API call *should* fail! 🚫 Standardization brings the consistency that admins and developers rely on for a true cloud native experience and helps with: ✨ Consistency Across Environments Run your workloads anywhere without worrying about the specifics of your environment. Kubernetes abstracts the complexity, providing a consistent experience. 🔌 Decoupling Superpower CRI, for example, decouples Kubernetes from specific container runtimes, supporting multiple options for performance, security, and flexibility. Build for your desired state with ease. 🔗 Layered Approach for Flexibility High-level and low-level runtimes work together, enhancing Kubernetes' adaptability and scalability. Moreover, you can use whatever you find best without any vendor lock-in. Switching is easier if required 🚀 Takeaway: Interfaces like CRI, CNI, and CSI enable Kubernetes’ modularity, making it more scalable, flexible, and interoperable. 💡 #Kubernetes #CloudNative

39

Rolling out all the infrastructure with Sander Trijssenaar for Global DevOps Experience! 600 teams will get a GitHub repository, Teams, CI/CD pipelines, Azure Resources (App services / storage accounts, etc.) 🤩✨. Tonight we will start (follow the sun, so staring in Australia) for ~36 hours of practicing what DevOps can bring for you and your team! With challenges around CI/CD, coding environments, GitHub Copilot, and even includes Azure OpenAI! Our infrastructure effort is now running to deploy all the resources for those teams so they can get started with a fully setup environment, and then learn the power of modern DevOps practices (like how easy it is to fix things if you have the control and trust to do so!). Can't wait for the teams to get started, looking forward to loads of fun! Below is a screenshot of the concurrent jobs that are running, and this is just the infra deployment part 💥. #gdex24 #github #xebia

17

Check this new Lightboard video with Robert Kloosterhuis! In this video, Robert, Technologist for Cloud-Native platforms, will show how the ‘IAAS Control Plane’ (formerly known as ‘vSphere with Tanzu’) can be enabled, and what kinds of deployment options you have available, including, new to vSphere8U3, on top of vSphere Stretched Clusters with vSAN - https://lnkd.in/gAzJb52H #cloudnative #IAAScontrolplane #vspehere8u3 #vsphere #stretchedclusters #vsan

1

Check this new Lightboard video with Robert Kloosterhuis! In this video, Robert, Technologist for Cloud-Native platforms, will show how the ‘IAAS Control Plane’ (formerly known as ‘vSphere with Tanzu’) can be enabled, and what kinds of deployment options you have available, including, new to vSphere8U3, on top of vSphere Stretched Clusters with vSAN - https://lnkd.in/gAzJb52H #cloudnative #IAAScontrolplane #vspehere8u3 #vsphere #stretchedclusters #vsan

1

Check this new Lightboard video with Robert Kloosterhuis! In this video, Robert, Technologist for Cloud-Native platforms, will show how the ‘IAAS Control Plane’ (formerly known as ‘vSphere with Tanzu’) can be enabled, and what kinds of deployment options you have available, including, new to vSphere8U3, on top of vSphere Stretched Clusters with vSAN - https://lnkd.in/gAzJb52H #cloudnative #IAAScontrolplane #vspehere8u3 #vsphere #stretchedclusters #vsan

10

Kubernetes: Past, Present, and Future. It’s been quite a while since k8s was originally published to the public and it’s changed a lot. From new APIs to new methods of running workloads on Kubernetes (like VMs), the landscape has increased rapidly. In this throwback episode of the Kubernetes Unpacked podcast, Kristina and I break down the k8s lifecycle. https://buff.ly/4aKO4JN #kubernetes #devops #platformengineering

8

Shifting 1000s of resources to Terraform Code manually can sometimes feel like emptying an ocean with a spoon. No matter how much you do, the end feels nowhere in sight. That's where ControlMonkey comes into play. 🐒 🍌 Our AI-powered Terraform Import Engine automatically detects all the unmanaged cloud resources throughout the accounts and generates 100% validated Terraform Code alongside the State File in a few clicks. ControlMonkey shortens the Terraform Import time by 70%, saves thousands of hours of manually writing Terraform Code, and accelerates the organization's shift to being fully GitOps. With ControlMonkey, you can shift 1000s of resources to Terraform Code in a few clicks. Learn more: https://lnkd.in/ddaUjexm #devops #iac #terraform #sre #gcp #aws #azure

15

KubeVirt is a way to run VMs on Kubernetes. No, not resources in Pods (like a container), but actual Virtual Machines. It creates a new resource via the KubeVirt CRDs that is a VM-based object, not a container. In this quick 5 minute article, you'll learn how to install it on any Kubernetes cluster. https://buff.ly/47vDRRm #kubernetes #devops #platformengineering

70

1 commentaar

I have a question. If you use a GitOps approach with Kubernetes and you use helm charts, how do you handle versions of the chart when you need to release? The reason I'm asking is that I see a lot of companies that updates the helm chart version only because the docker image tag needs to be bumper to the new version. Then they do a pull request in a GitOps repository for the change to take effect. But why update a helm chart just because one input variable changed? Nothing in the templating part changed. It seems extremely unnecessary yet tons of companies do it. What am I missing? We simply add the new tag as a value (like --set in a prompt) in the helmRelease object/yml file.

58

65 commentaren

🚀 Dive into the future of AI-powered software development at the GitLab DevSecOps World Tour Amsterdam on Monday, November 25! The morning sessions will feature strategic insights from GitLab executives and customer success stories that demonstrate tangible business impact. The afternoon deep dives will offer focused breakout sessions on implementation strategies and exchange best practices. 🎯 Who should attend: 👉 Executives & Engineering Leaders 👉 GitLab Users & Practitioners ✨ Registration is FREE—bring your team and level up together! Sign up here https://lnkd.in/eWncTkfu #GitLab #DevSecOps #AI

12

If you've been eagerly waiting for Chapter 2 of our new "Wizard's Journey Through the Technical Inner Workings of Kubernetes Resource Management," the 🧙 has landed! In Chapter 2, Reid Vandewiele takes you on a deep dive into CPU that explores how CPU resource requests and limits come into play at the Linux OS level. Check it out on The New Stack ! https://lnkd.in/ebsXvk6T

6

1 commentaar

🚀 New on my blog: Terraform + OpenAI in Azure! 🌐 Ever wondered how to deploy an OpenAI service in Azure using Terraform? In my latest blog post, I walk you through the process step-by-step, showing you how to set it up and interact with the public endpoints for your prompting needs. Whether you’re a cloud newbie or a seasoned DevOps pro, this guide should support you! Check it out here: https://lnkd.in/d2YZtn2e #MVPBuzz #HashiCorpAmbassador #Terraform #Azure #OpenAI #Cloud #DevOps #TechBlog

8

Want to know more about Terraform and OpenTofu locals? Check out some real-world use cases in our blog: https://lnkd.in/eWHXQUqD

6

well rounded and balanced discussion of apply/merge precedence, as usual, other factors impact the final decision

2

Terraform's Import block functionality will help give a lot of companies the ability to bring their existing infrastructure under a unified code base. Now with the ability to use for_each inside their import block this video shows a cool way to utilize that feature to build on top of your existing pipelines without having to re-engineer anything.

4