We are announcing the deprecation of Dispatch, our DKP 1.x CI/CD tool, based on Tekton and ArgoCD. As another step in the continuous improvement of the DKP platform, in DKP 2.0 we have made the move to FluxCD, a CNCF incubator project. Why did we make this decision? Our customers have significant investments in their build pipelines using battle tested technologies such as Jenkins, TeamCity, and CircleCI. It would be a significant change in their workflows to introduce a new CI tool like Tekton.

We are excited to announce Calico Enterprise 3.9, which provides faster and simpler live troubleshooting using Dynamic Packet Capture for organizations while meeting regulatory and compliance requirements to access the underlying data. The release makes application-level observability resource-efficient, less security intrusive, and easier to manage. It also includes pod-to-pod encryption with Microsoft AKS and AWS EKS with AWS CNI.

We are pleased and proud to announce the General Availability of D2iQ Kaptain 1.2. This new update includes new features and improvements to the overall user experience, including: The new dashboard enables users to visually monitor and observe the resource consumption of Kaptain Workloads, observe the state of those workloads, and easily identify and debug any issues.

This blog can provide you with useful information on how to set up a Kubernetes CI/CD workflow using state-of-the-art of open source DevOps tools, whether you are.

One of the foundations of GitOps is the usage of Git as the source of truth for the whole system. While most people are familiar with the practice of storing the application source code in version control, GitOps dictates that you should also store all the other parts of your application, such as configuration, kubernetes manifests, db scripts, cluster definitions, etc. But what about secrets? How can you use secrets with GitOps?