Containers are no longer the next big thing in the industry. They are mainstream now. This means they should be treated seriously and not like a novelty. What are the main areas of concern when you want to add a new tool to your stack? For most of us stability, security, and observability are the things that matter the most. This article will focus on security.
Today we are proud to announce Submariner, a new open-source project enabling network connectivity between Kubernetes clusters. We launched the project to provide network connectivity for microservices deployed in multiple Kubernetes clusters that need to communicate with each other.
One of my former teammates approached me the other day (and by other day i mean like 3 months ago) and asked ‘Am I thinking about this right? Kubernetes is actually akin to the Linux Kernel. So Rancher and OpenShift are distributions of Kubernetes. And for a supported enterprise application I’m more likely to use a more enterprise focused distribution than a DIY distribution, yeah?’ To which I responded ‘Yep, you hit the nail on the head’.
Today’s applications are marvels of distributed systems development. Each function or service that makes up an application may be executing on a different system, based upon a different system architecture, that is housed in a different geographical location, and written in a different computer language.
We are very excited to announce Calico v3.6. Here are some highlights from the release.
In the new cloud-native world, ephemeral services like containers make security a challenging task. As enterprises start adopting containers in production, they suffer from a great deal of variance in the software, configuration, and other static artifacts that exist across their organization’s container image set.
Container adoption in IT industry is on a dramatic growth. The surge in container adoption is the driving force behind the eagerness to get on board with the most popular orchestration platform around, organizations are jumping on the Kubernetes bandwagon to orchestrate and gauge their container workloads.
Servers are expensive. And in single-application installations, most servers spend the majority of their time waiting. Making the most of these expensive assets led to virtualization, and making the most of virtualization has led to multiple options for virtualizing applications. VMware and Docker offer competing methods for virtualizing applications. Both technologies work to make the most of limited hardware resources, but they do so in significantly different ways.
Containers are fast becoming the defacto standard as a building block for creating and deploying applications. Containerization allows development teams to have consistent environments, cost optimizations, isolation, and versatility, in general. The open-source Containerd project is a critical component for the modern cloud-native containerized landscape, providing a runtime that is widely used in millions of applications every day.
In an attempt to jump on the Kubernetes bandwagon, more and more managed Kubernetes services are being introduced. In a previous post, we explored how to deploy a Kubernetes cluster on Amazon EKS. This time, we will cover the steps for performing a similar process, this time on Google’s Kubernetes Engine.
