What’s cooking in your Kubernetes namespace?

kubectl connections <ResourceType> <ResourceName> <NamespaceName>
kubectl connections ServiceAccount default kube-system
  • Even though all the three Kubernetes versions are 1.17, each cluster’s makeup is different. Some provide the cluster where some of the operational software is already running, for example logging (fluent), monitoring (prometheus), networking (cilium).
  • These outputs show us that the number of Pods running in the kube-system namespace can differ based on what functions are provided on a cluster out-of-the-box. This can affect your decision on how much resources (CPU/Memory) to allocate for your control plane nodes in the cluster.
  • DNS Pod is present everywhere and it makes sense as DNS is probably one of the most important functions that needs to work out-of-the-box on a cluster.





Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Crodo.io. Latest news

My Opinion on Flutter

Setting a Light Scene for watching Netflix with Home Assistant

Relationships are Complicated: Rails Active Record Associations

Running Jenkins ci/cd deployments in an IBM Cloud private environment

Computational Law Diary: Lollies, Decision Tables, and What “Hamilton” Teaches Us About…

The words “The Search Space” over a 3d model of a complicated spherical structure.

My Web Development Journey

Team Page Redesign — Redefining Corporate Hierarchy

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store



More from Medium

Kubernetes upgrade ‘The Hard-Way’

Helm — Package Manager for Kubernetes

K8’s — Kubernetes

Canary Deployment in Kubernetes (Part 1) — Simple Canary Deployment using Ingress NGINX