It’s that time of year again, the time for retrospective articles and “Top 10 of the Year” posts. We decided to focus our recap on how CVEs and changes in the threat landscape affected Kubernetes in 2019, and what changes that brought about inside of Rancher. Throughout 2019, solutions across the CNCF stack prioritized security and brought it to the forefront of both mind and action.

In our previous blog post, we discussed how investments in AIOps platforms have been justified on the basis of their ability to decrease mean time to problem resolution and the resultant cost reduction. But one of the challenges most IT Ops teams face is in the approach of deploying AIOps solutions for business-critical use cases: Where do we start? Some use AIOps to analyze unstructured data in order to identify higher-level correlations that traditional IT monitoring tools wouldn’t be capable of.

We’re excited to release version 7 of the Datadog Agent. It has all of the same functionality as Agent 6, but it is the first version to ship with only the Python 3 runtime. With Python 2 reaching its end of life on January 1, 2020, migrating your services to Python 3 will ensure that they continue working as expected. We’ve tested all of our more than 350 integrations to ensure they work with Python 3.

Cilium is an open source technology that delivers network security to large-scale containerized environments at the packet and application levels. Cilium integrates easily with your Kubernetes clusters, either self-managed or managed services (e.g., Amazon EKS, Google GKE, and Microsoft AKS). You can also deploy Cilium to Docker environments using Mesos.

There are scenarios where we want to de-couple logic across multiple logic apps. Generally, this is a straight forward endeavor, unless the downstream logic app has a long-running process. When this does occur, the client (or publisher) will experience an HTTP timeout if the request takes more than 2 minutes. This scenario is captured within the Azure Logic Apps documentation.

If you are a developer, a systems administrator, you work in the information technology sector or you are simply a technology enthusiast who has ever deployed some type of application, surely you will have faced the same problem we all ran into. If you are thinking of dependencies, bingo!

Tools. As engineers we all love great tools that help our teams work productively, resolve problems faster, be better. But tools can tend to grow in number, require additional maintenance, and most importantly, create silos. Each team has certain responsibilities and is constantly searching for tools that can address specific requirements in the best possible way.

At Sentry, we’re big fans of continuous integration and deployment. We’re also big fans of GitHub — and not just because we employ a number of notable GitHub alumni. We use our own GitHub integration to link issues, identify suspect commits that likely introduced new errors, and suggest assignees who can best resolve each issue. Last month, GitHub released GitHub Actions for general availability.

In our previous blog post, we discussed how we are approaching an important inflection point in the cloud migration timeline. Certain legacy applications will remain on owned infrastructure for the foreseeable future, but the scale and agility offered by cloud platforms offers competitive and operational advantages that most organizations cannot ignore. As cloud adoption became mainstream, many enterprises saw fewer objections to migrating their infrastructure to cloud.