It comes as no surprise that the demand for Kubernetes is skyrocketing across the industry. According to the CNCF’s 2019 survey, 78% of respondents are using Kubernetes in production today. This growth is contributing to a surge of demand for talent: there are over 100 thousand cloud native job postings across Dice and Indeed alone. The talent pool of people that have worked with Kubernetes and the adjacent technologies is limited and demand is growing.
Responsibilities are shifting between software developers and operators due to the increasing adoption of agile development practices, DevOps, and GitOps. This makes it challenging for developers and operators to effectively collaborate in order to increase developer agility and productivity. D2iQ’s Dispatch is built on a cloud native foundation, leveraging Tekton and Argo CD to simplify running CI/CD on Kubernetes with a simplified user experience.
GitOps has been around for quite some time now and continues to pique developer interest when it comes to driving operation tools. This technology-agnostic model embraces operations best practices, using Git as a single source of truth for declarative infrastructure and applications.The term GitOps for this operating model is now an industry standard and has rapidly made a name for itself among the Kubernetes and cloud-native communities.
We are proud to announce the general availability of DC/OS 2.1, which includes new enterprise-grade capabilities across the following key areas. These new capabilities further enhance the standing of DC/OS as the most robust, scalable cloud native platform for enterprises.
Despite the difficulties we’ve all experienced during this pandemic, it has been fascinating to watch how human beings have come together as communities all over the world to support each other, and our Cloud Native community is no different.
A security vulnerability (CVE-2020-8555) with a Medium severity has been reported that affects following versions of Kubernetes: Note, an attack using this vulnerability requires permission to create a pod or StorageClass and would typically only be granted to internal administrators or developers within an organization. It is possible to mitigate an attack by implementing policies using Gatekeeper and restricting StorageClass using Kubernetes access controls.
