Operations | Monitoring | ITSM | DevOps | Cloud

If you happen to be running multiple clusters, each with a large number of services, you’ll find that it’s rather impractical to use static alerts, such as “number of pods < X” or “ingress requests > Y”, or to simply measure the number of HTTP errors. Values fluctuate for every region, data center, cluster, etc. It’s difficult to manually adjust alerts and, when not done properly, you either get way too many false-positives or you could miss a key event.

Docker and Kubernetes have taken the software world by storm. DevOps, containers, and container management are at the center of most conversations about what’s relevant to technology. Tooling and services that ease running software in containers, therefore, occupy the minds of developers. Great tools and platforms create options and possibilities. They also create challenges in understanding available choices, though.

The round was led by Peterson Ventures, with participation from new investors Prelude Venture Fund, SaaS Ventures, and Forward Venture Capital and participation from existing investors Trilogy Equity Partners and Cobre Capital. It has been amazing to see the positive feedback we’ve received from our customers as we work to make the first fully automated infrastructure monitoring and alerting solution.

Kubernetes security tools … there are so freaking many of them; with different purposes, scopes and licenses. That’s why we decided to create this Kubernetes security tools list, including open source projects and commercial platforms from different vendors, to help you choose the ones that look more interesting to you and guide you in the right direction depending on your Kubernetes security needs.

A recent CNCF-sponsored Kubernetes security audit uncovered CVE-2019-11246, a high-severity vulnerability affecting the command-line kubectl tool. If exploited, it could lead to a directory traversal, allowing a malicious container to replace or create files on a user’s workstation. This vulnerability stemmed from an incomplete fix of a previously disclosed vulnerability (CVE-2019-1002101). Are you vulnerable?

We are very excited to announce Calico v3.8. Here are some highlights from the release. You can now view IP address usage for each IP pool using calicoctl. This allows you to more easily manage the IP space in your cluster, providing a simple way to see which IP pools have addresses available and which are running low. See the calicoctl reference documentation for more detailed information on how to use this feature.

Kubernetes is the de facto industry standard for container management and orchestration. Not surprisingly, it has also become common to use Kubernetes in tandem with compatible Continuous Integration (CI) and Continuous Deployment (CD) tools. As a container orchestrator, Kubernetes expects deployments to spin up software throughout a cluster. Those deployments are created using files or command lines that can be generated manually or using properly configured CI/CD software.

Cycle aims to give you maximum flexibility with how you architect your application. By marking a container as ‘stateful’, you’re declaring that the container and its instances should be treated more like pets than cattle, but more on that analogy below. The need to maintain state should never be a deciding factor when considering whether or not to containerize as containers are simply portable code packages.

In a Kubernetes cluster, the machines are divided into two main groups: worker nodes and master nodes. Worker nodes run your pods and the applications within them, whereas the master node runs the Kubernetes Control Plane, which is responsible for the management of the worker nodes. The Control Plane makes scheduling decisions, monitors the cluster, and implements changes to get the cluster to a desired state.