In the wake of Broadcom’s acquisition of VMware, the world of virtualization is in flux. Customers, especially those reliant on VMware’s Pivotal Cloud Foundry (PCF), are feeling uncertain about the future. This blog post is designed to guide customers through the specific hurdles they now face due to the acquisition, explore Kubernetes (K8s) as an alternative to PCF, and discuss how Komodor can help with a K8s migration.

We are proud to announce that Qovery has been officially accepted into the AWS ISV Accelerate Program as of October 21, 2024. This strategic achievement is a game changer for both Qovery and our customers, offering new avenues for collaboration and growth through an integrated go-to-market approach with AWS.

In the ever-evolving DevOps and site reliability engineering (SRE) landscape, Kubernetes stands out as a pivotal technology, revolutionizing how we deploy, scale, and manage containerized applications. K8s offers powerful orchestration capabilities, ensuring our applications are resilient and can scale seamlessly to meet varying demands. However, as robust as Kubernetes is, managing it efficiently requires significant expertise and effort.

When selecting a cloud migration partner, it’s essential to evaluate their capabilities, experience, and alignment with your business needs. Here’s a guide on what to look for.

Kubernetes has become the dominant orchestration platform for cloud-native apps– and for good reason. It can be a powerful tool in your software development lifecycle. But how do you know if your Kubernetes-based app can handle the demands of production traffic? Kubernetes alone isn’t always enough to ensure your app’s performance under load. In many cases, it is, but it’s always wise to know your application’s limits.

In a dynamic environment like Kubernetes, where manual tracking is impossible, AI-powered monitoring tools, such as Site24x7, surf through enormous amounts of data, detecting irregularities, predicting vulnerabilities, and alerting the user about a possible outage that is about to happen if the resource is not handled.

Let’s be real, we’ve never been huge fans of conventional unstructured logs at Honeycomb. From the very start, we’ve emitted from our own codestructured wide events and distributed traces with well-formed schemas. Fortunately (because it avoids reinventing the wheel) and unfortunately (because it doesn’t adhere to our standards for observability) for us, not all the software we run is written by us.

At some point, your development team may be considering implementing load testing (also known as stress testing) as part of your software testing process. Load testing validates that your web app is able to withstand a large number of simultaneous users, decreasing the chance that any traffic spikes will bring down your services once deployed. These stress tests can be highly granular, giving you the opportunity to test run virtually unlimited strategies before they are set into the wild.

One of Argo CD’s standout features is its powerful user interface (UI) that shows the live status of all applications and the respective Kubernetes resources. Both developers and operators can quickly understand the status of their deployments by looking at the UI and drilling down into all the different views of Argo CD applications. Some teams even use the Argo CD UI as a generic Kubernetes dashboard and management interface (especially after the addition of the web-based terminal feature).

GoReplay and Speedscale are two popular tools commonly used for load testing. Both share traffic shadowing as a core feature. This article compares both tools against the following criteria: For more Kubernetes load testing comparisons, check out our other posts.