Operations | Monitoring | ITSM | DevOps | Cloud

As the container orchestration platform of choice for many enterprises, Kubernetes (or K8s, as it’s often written) is an obvious target for cybercriminals. In its early days, the sheer complexity of managing your own Kubernetes deployment meant it was easy to miss security flaws and introduce loopholes. Now that the platform has evolved and been managed, Kubernetes services are available from all major cloud vendors, and Kubernetes security best practices have been developed and defined.

Implementing change in an organization always has its challenges, and for it to be successful it requires support from executive management. For one of our large Managed Service Provider (MSP) clients, their new CIO was focused on making their customer’s cloud consumption more efficient, with the outcome being cost savings.

Terraform combined with Qovery is like giving superpower to DevOps and developers. I am super excited to launch a brand new GitHub repository with "ready-to-use" examples to deploy crazy AWS cloud architecture with Terraform and Qovery. Feel free to use them, modify them and share them with us and our community.

It’s no secret that AWS has an extensive catalog of services which enable organizations to rapidly scale infrastructure. In this fast paced and self scaling cloud native world, observability across all these services has never been more critical. As a long time AWS Technology Partner, it’s always great to speak to our friends at AWS, and most recently, Lumigo CEO Erez Berkner joined AWS on Air to talk about end-to-end observability of the modern cloud application.

Organizations are moving from monolithic architecture (where all the code building the application exists as a single, monolithic entity) to microservices architecture as it simplifies app management, making it easier to build, deploy, update, test and scale each service independently without affecting other parts of the architecture.

Hi everyone, Albane here 👋 If you read my changelogs, you probably realized that I have been talking about a V3 in the making; almost a year after our V2, the wait is almost over because after gathering all of your precious feedback and nearly a quarter of work the Alpha testing is coming before the end of the month! 🤩 This V3 is undoubtedly the most significant product evolution of the last twelve months, but what’s so special about it?

It’s right there on our community page—the statement that “Project Calico is first and foremost a community.” With that in mind, we wanted to make it easier for new contributors to get involved. It’s a win-win scenario—developers experience less frustration, they can get their work done, and have their contributions considered. Plus, the project can easily benefit from the contributions.