101 private links
Ifyou go around and ask for a Kubernetes expert, whoever responds to your call is definitely lying. They probably are an expert in one of the many components that make a Kubernetes cluster, but I bet you there is a complete section of Kubernetes they have not touched or even heard about.
Not saying that Kubernetes is complex without reason, because it has its reasons, but it is a complex beast.
Network controllers seems to be one of those components that only very few people know how they truly work, or at least I couldn’t find many during my search for answers, and once you decide on one, and get yours up and running, you pretty much forget about it.
At Blend, we make extensive use of Kubernetes on AWS to power our infrastructure. Kubernetes has many moving parts, and most of these components are swappable, allowing us to customize clusters to our needs. An important component of any cluster is the Container Network Interface (CNI), which handles the networking for all pods running on the cluster. Choosing the right CNI for each use case is critically important and making changes, once serving production traffic, can be painful. Blend had several problems with the CNI we initially chose (Weave), leading us to explore alternatives. We eventually decided to switch and in this post, we describe the challenges and solutions to migrating without downtime.
Zero configuration or integration required — just launch and go.
Weave Scope automatically detects processes, containers, hosts. No kernel modules, no agents, no special libraries, no coding. Seamless integration with Docker, Kubernetes, DCOS and AWS ECS.
Weave Scope automatically generates a map of your application, enabling you to intuitively understand, monitor, and control your containerized, microservices-based application.
A kubectl plugin that utilize tcpdump and Wireshark to start a remote capture on any pod in your Kubernetes cluster.
You get the full power of Wireshark with minimal impact on your running pods
The next level of chaos engineering is here! Kill pods inside your Kubernetes cluster by shooting them in Doom!
This is a fork of the excellent gideonred/dockerdoomd using a slightly modified Doom, forked from https://github.com/gideonred/dockerdoom, which was forked from psdoom.
This article assumes a basic knowledge of Docker. This is the first article in a series of posts called “Simplified”, where I take a look at systems that I think aren’t adequately explained in their own “getting started” documentation. Today, I’m taking a look at one of the most complicated systems I’ve used to date.
Practical Kubernetes Problems
This repo provides some resources to learn Kubernetes through practical exercises for our Kubernauts' Kubernetes trainings or for self study to learn how easy it is to understand and master Kubernetes complexity and problems.
Kubernetes is easy to understand, even if it looks hard at the first look on the icons or the resources map, this course is about to help you to understand K8s and learn how to start!