I am excited to announce the partnership between Qovery and Doppler. Qovery is an infrastructure automation platform that helps developers deploy their applications more easily, while Doppler is a fully managed SecretOps platform that enables engineering teams to better manage their environment variables and secrets.

When containers and container orchestration were introduced, they opened the possibility of helping companies utilize physical resources like CPU and memory more efficiently. But as more companies and bigger enterprises have adopted Kubernetes, FinOps professionals may wonder why their cloud bills haven’t gone down—or worse, why they have increased.

D2iQ has made available a new assessment tool that enables you to gauge your container management maturity level. By taking a 1-minute quiz, you can identify where you fit within the five levels of cloud-native container-management maturity–Explorer, Beginner, Intermediate, Advanced, and Master. The maturity model is based on the wisdom of D2iQ Kubernetes experts with more than a decade of experience building and deploying Kubernetes platforms for customers.

Today, I'm excited to share with you how we've turned Kubernetes into a product that developers can easily use without any headaches. We'll explore why Kubernetes can be difficult for developers and how Qovery simplifies the process by acting as an intermediate layer and integrating with the developer ecosystem.

Kubernetes Monitoring in Grafana Cloud is already an observability Swiss Army knife: You can monitor your Kubernetes fleet performance, nodes, pod logs, resource utilization, and overall infrastructure health all in one hosted platform that comes with prebuilt Grafana dashboards to visualize all the important telemetry you need. All of this sounds great … but what if you already have Grafana dashboards and alerts that are custom to your fleet and the way you do business?

Kubernetes vs OpenStack is a common dilemma that organisations face when considering the modernisation of their IT infrastructure. Both are well-established open-source technologies for building cloud infrastructure, and both bring tangible benefits, especially when used in combination. Yet, they differ significantly and need to be properly bundled to feel like a fully-integrated solution. What does this mean in practice? Let’s take a look!

In a prior blog post, we discussed the basics of Kubernetes Limits and Requests: they serve an important role to manage resources in cloud environments. In another article in the series, we discussed the Out of Memory kills and CPU throttling that can affect your cluster. But, all in all, Limits and Requests are not silver bullets for CPU management and there are cases where other alternatives might be a better option.