The previous post in this series took a deep dive into setting up IP Fabric on Cumulus VX and spinning up a Kubernetes cluster connected to it. This post focuses on one of the scenarios available for Calico and Kubernetes deployment. (Our next post looks at a second scenario; the start of this series walked you through a history of data centre networking and Calico for Kubernetes.)

Previously in this blog post series, I walked you through a bit of history of data centre networking and introduced Calico for Kubernetes. This blog post deep dives into setting up IP Fabric on Cumulus VX and spinning up Kubernetes cluster connected to it.

One day, you may be tempted to build and maintain an on-premises Kubernetes cluster. Don’t do it. That's my best advice. Instead, take a look at the managed cloud provider options like GKE, AKS, and EKS , which take away a lot of the pain and expense involved in maintaining and updating Kubernetes clusters. However, sometimes legal or business requirements mean that it's essential that your cluster runs on prem.

In its Aristotle project, Google tried to define the success of effective teams. The researchers’ main finding was that what really mattered was less about who is on the team, and more about how the team worked together. Most important in teamwork was the presence of psychological safety.

We need to talk.

No, really—one of the hardest parts of wrapping your head around the complexities of CloudNative is getting a handle on all the lingo. Containers, microservices, and orchestration, oh my! When Container Solutions staff meet with clients, we often find that the best place to begin is with a quick Cloud Native 101 to make sure we are all talking about the same things in the same way.