Operations | Monitoring | ITSM | DevOps | Cloud

In a previous post, we talked about the increasing adoption of Platform Engineering teams. The post covered topics such as defining Platform Engineering and the roles and responsibilities of the team. When building an internal platform, a clear goal that many teams want to achieve is: Even though this is key to a successful platform team, this responsibility increases complexity, costs, support time, and more. Not to mention that this can be a long, very long journey.

With the advent of IaaS (Infrastructure as a service) and IaC (Infrastructure as Code), it is now possible to manage versioning, code reviews, and CI/CD pipelines at the infrastructure level through resource provisioning and on-demand service routing. Kubernetes is the indisputable choice for container orchestration.

Congratulations to the Kubespray team on the release of 2.17! This release brings support for two of the newer features in Calico: support for the eBPF data plane, and also for WireGuard encryption. Let’s dive into configuring Kubespray to enable these new features.

Not to muddy the waters with one more prefix in front of ops, GitOps is a newer DevOps paradigm that slants towards the developer. As the names states, GitOps is focused around Git, the source code management tool. As a developer, leveraging an SCM is one of the quintessential tools of the trade; allowing for collaboration and more importantly saving your hard work off of your machine.

After nearly 2 years of perfecting our product during our beta phase and just over 5 months since we opened for early access, I have great pleasure in announcing that Civo is now 'General Availability'. It's taken us over 4 years to get to where we are today, with a colossal amount of work being contributed by our team to build the Civo platform and developer eco-system. I can honestly say that we're lucky to have so many amazing people at Civo.

After nearly 2 years of perfecting our product during our beta phase and just over 5 months since we opened for early access, I have great pleasure in announcing that Civo is now 'General Availability'. It's taken us over 4 years to get to where we are today, with a colossal amount of work being contributed by our team to build the Civo platform and developer eco-system. I can honestly say that we're lucky to have so many amazing people at Civo.

Today, just in time for Kubecon 2021, I am happy to announce the beta availability of Workflows. For me, this is our most exciting product announcement to date – a completely new capability that expands the definition of what Komodor is, as it charts the course for its next evolution. Let me start with the feature first. In a nutshell, Workflows is a series of smart algorithms that operate within the “depths” of Komodor.

Shipa can be deployed on most Kubernetes environments (EKS, GKE, AKS, OKE, Linode, minikube and so on). How about k3s? Let us try to deploy WordPress on k3s cluster using Shipa. We are going to use k3d to create a k3s Kubernetes cluster.

Transparency is essential when running production infrastructure. As we are onboarding more and more customers, we strive to make Qovery as open as possible and fully transparent on how it manages your applications. Check out our updated documentation to learn more on how Qovery works.