Whether running on the public cloud or a private cloud, the use of containers is ingrained in today’s devops oriented workflows. Having workloads set up to run under the mandated compliance requirements is thus necessary to fully exploit the potential of containers. This article focuses on how to build and run containers that comply with the US and Canada government FIPS140-2 data protection standard.

Docker v20 was officially released a few months ago, bringing new features that will make your builds faster and more secure. We will be progressively rolling out the new version to Bitbucket Pipelines throughout the month of June 2021.

During the next five weeks, our team will work to improve the overall experience of Qovery. We gathered all your feedback (thank you to our wonderful community 🙏), and we decided to make significant changes to make Qovery a better place to deploy and manage your apps. This series will reveal all the changes and features you will get in the next major release of Qovery. Let's go!

On our cloud-native journey, we live in a containerized world. Our environments are containers, managed by orchestrators, and living on some level of computing clusters. Of course, that means you are also responsible for managing all those bits, right?

The CVE-2021-20291 medium-level vulnerability has been found in containers/storage Go library, leading to Denial of Service (DoS) when vulnerable container engines pull an injected image from a registry. The container engines affected are: Any containerized infrastructure that relies on these vulnerable container engines are affected as well, including Kubernetes and OpenShift.

Telepresence 2 was recently released and (like Telepresence 1) it is a worthy addition to your Kubernetes tool chest. Telepresence is one of those tools you cannot live without after discovering how your daily workflow is improved. So what is Telepresence? It is too hard to describe all the functionalities of the tool in a single sentence, but for now I would describe it as the “Kubernetes swiss army networking tool”.

If you’re a developer, a DevOps engineer or just a person fascinated by the unprecedented growth of Kubernetes, you’ve probably scratched your head about how to get started. MicroK8s is the simplest way to do so. Canonical’s lightweight Kubernetes distribution started back in 2018 as a quick and simple way for people to consume K8s services and essential tools.

Argo Rollouts is a progressive delivery controller created for Kubernetes. It allows you to deploy your application with minimal/zero downtime by adopting a gradual way of deploying instead of taking an “all at once” approach. Argo Rollouts supercharges your Kubernetes cluster and in addition to the rolling updates you can now do In the previous article, we have seen blue/green deployments.

IBM’s AIX operating system has powered zillion mission-critical applications for over three decades, providing enterprise applications the edge to do more. And, let’s not forget that a huge chunk of BFSI applications is still nesting on AIX within their own data centers due to its security, performance, and reliability.

If your organization is adopting multiple Kubernetes clusters, chances are that multiple users or groups have access to these clusters on the same shared infrastructure. Kubernetes multi-tenancy aims to drive efficient use of infrastructure, while providing operators with robust isolation mechanisms between users, workloads, or teams. Running more applications on the same shared infrastructure means better utilization of resources and a reduction in overall operating costs.