This article is part of our series “Codefresh in the Wild” which shows how we picked public open-source projects and deployed them to Kubernetes with our own pipelines. This week’s pick is starbase-80, a Kubernetes “homepage” application. We will use various tools such as GitHub, Docker, AWS, Codefresh, Argo CD, Terraform. This article chronicles how we integrated all those tools together in order to build an end-to-end deployment workflow.

This article is part of our series “Codefresh in the Wild” which shows how we picked public open-source projects and deployed them to Kubernetes with our own pipelines. This week’s pick is draw.io an online application for drawing different types of diagrams. We will use several tools such as GitHub, Docker, Helm Codefresh, Argo Rollouts, Argo CD. This guide chronicles how we integrated all those tools together in order to build an end-to-end Kubernetes deployment workflow.

At Qovery, we build our frontend using Nx and rely on the official nrwl/ci GitHub Actions. Our frontend requires third-party tokens during compile time, but we would like to avoid hardcoding them or using the.env file to define our tokens. The latter exposes our source code directly on GitHub, and even though it's not sensitive data, we don't want it to be easily scraped.

Reliability risks are potential points of failure in your system where an outage could occur. If you can find and remediate reliability risks, then you can prevent incidents before they happen. In complex Kubernetes systems, these reliability risks can take a wide variety of forms, including node failures, pod or container crashes, missing autoscaling rules, misconfigured load balancing or application gateway rules, pod crash loops, and more. And they’re more prevalent than you might think.

The evolution of cloud infrastructure management has been significantly influenced by the development of Infrastructure as Code (IaC) tools, among which Crossplane stands out as a pioneering solution. CrossPlane, an open-source project, revolutionizes how developers manage and orchestrate cloud services by extending Kubernetes with powerful abstractions for multi-cloud environments.

This article is part of our series “Codefresh in the Wild” which shows how we picked public open-source projects and deployed them to Kubernetes with our own pipelines. We will use several tools such as GitHub, Docker, AWS, Codefresh, Argo CD, Kustomize. This guide chronicles how we integrated all those tools together in order to build an end-to-end Kubernetes deployment workflow.

Deploying Kubernetes in production environments at scale is a common enterprise challenge. Learn how Cisco and Spectro Cloud ease deployment and management of Kubernetes clusters in the cloud, bare metal and virtualized data center, and at the edge.

Container orchestration, Kubernetes has emerged as a leading platform for managing and deploying containerized applications. One fundamental concept that plays a crucial role in ensuring optimal performance is the Quality of Service (QoS). In the realm of Kubernetes, this concept is applied at the level of Pods, forming the backbone of resource management within the cluster.

In the context of utilizing physical servers, the complete resources often remain underutilized, and even in the case of laptops, optimal resource utilization is not achieved. To address this challenge, technological advancements have led to the introduction to containers.

The Sysdig 2024 Cloud‑Native Security and Usage Report highlights the evolving threat landscape, but more importantly, as the adoption of cloud-native technologies such as container and Kubernetes continue to increase, not all organizations are following best practices. This is ultimately handing attackers an advantage when it comes to exploiting containers for resource utilization in operations such as Kubernetes.