While the Docker buzz has faded a bit, replaced by new words like “Kubernetes” and “Serverless”, there is no arguing that Docker is the default toolchain for developers looking to get started with Linux containers, as it is fairly ubiquitous and tightly integrated with a variety of platforms.

On October 22, 2020, Shipa launched a new web series called “Coffee & Containers.” C&C was conceived as a place for practitioners and IT leaders to learn and collaborate on all things microservices, cloud-native, containers, Kubernetes, etc. We were very proud to launch this series with Kelsey Hightower, Thought Leader and Developer Advocate at Google Cloud Platform, and Bruno Andrade, Founder and CEO of Shipa.io.

When making changes to applications these days, it’s hard to understand and predict the impact of those changes before you deploy. API connections are multiplying, and with new cloud platforms such as containers/serverless, it only add to the complexity. Some people have trouble remembering whether they closed the garage door or turned off the coffee maker. Can you remember all the details of your latest API contract change? Let alone who would be impacted and needed to be notified?

As we enter a new year, it’s an appropriate time to reflect on our achievements at Tigera and how much Calico Enterprise has evolved over the past year as the industry’s leading Security and Observability solution for Kubernetes Networking and Microservices.

Nowadays developers are in the driver’s seat regarding a lot of decisions for the tools they use. In this update from Tyler Jewell, he covers what he sees are the Top 5 trends that will take place this year. While it’s a bit of a crowded chart, he plots the companies that he sees driving these trends. If you drill into the Service Catalog trend, Jewell sees a couple of different groups working on ways to help developers deal with the deluge of Services (aka APIs).

This is the third and last part in our Kubernetes Anti-patterns series. See also part 1 and part 2 for the previous anti-patterns. You can also download all 3 parts in a PDF ebook.

This is the second part in our Kubernetes Anti-patterns series. See also part 1 for for the previous part and part 3 for the next part. You can also download all 3 parts in a PDF ebook.

In our previous guide, we documented 10 Docker anti-patterns. This guide has been very popular as it can help you in your first steps with container images. Creating container images for your application, however, is only half the story. You still need a way to deploy these containers in production, and the de facto solution for doing this is by using Kubernetes clusters. We soon realized that we must also create a similar guide for Kubernetes deployments.

Innovation in hypervisor technology in the early 2000’s from both commercial and open source projects was the genesis for the public cloud as we know it today. Virtualization and Moore’s law, together with advances in storage technology, mobile and wireless, created a data explosion that continues to accelerate through today.

In this blog, we will compare and contrast Falco vs. AuditD from a Host Intrusion Detection (HIDS) perspective. AuditD is a native feature to the Linux kernel that collects certain types of system activity to facilitate incident investigation. Falco is the CNCF open-source project for runtime threat detection for containers and Kubernetes. We will dig deeper into the technical details and cover the installation, detection, resource consumption, and integration between both products.