Discover and read the best of Twitter Threads about #Klustered
Most recents (3)
My top Twitter threads on cloud, containers, and microservices for this year so far:
- Platform engineering
- API gateway vs service mesh
- @Kubernetesio debugging
- @Docker chaos testing
- Fast dev/test with Telepresence
- @buildpacks_io
- Microservice testing
A 🧵 of 🧵 s 👇
- Platform engineering
- API gateway vs service mesh
- @Kubernetesio debugging
- @Docker chaos testing
- Fast dev/test with Telepresence
- @buildpacks_io
- Microservice testing
A 🧵 of 🧵 s 👇
I'm predicting big things for the "platform engineering" space over the next year. Whether you ❤️ or 😡 the name, I think this is the new DevOps.
Watch this space for lots of knowledge sharing, innovation, and VC money 💰 !
Watch this space for lots of knowledge sharing, innovation, and VC money 💰 !
A critical part of your platform is the communication infrastructure ☎️
I think there is a lot of innovation -- and potential confusion -- in the cloud native API gateway and service mesh spaces (and n/s vs e/w 🧭 )
I think there is a lot of innovation -- and potential confusion -- in the cloud native API gateway and service mesh spaces (and n/s vs e/w 🧭 )
In preparation for fixing broken Kubernetes clusters live on @rawkode's #Klustered event, I reminded myself of some of the core K8s debugging commands and techniques
Here are my top 10 tips for platform engineers debugging Kubernetes and the machinery underneath the covers 🧵 👇
Here are my top 10 tips for platform engineers debugging Kubernetes and the machinery underneath the covers 🧵 👇
First off, use kubectl to take a look at the cluster infra:
$ kubectl get nodes
$ kubectl cluster-info dump
These commands typically give you a good idea of where to start debugging, e.g. broken nodes, infra issues, resources
$ kubectl get nodes
$ kubectl cluster-info dump
These commands typically give you a good idea of where to start debugging, e.g. broken nodes, infra issues, resources
If kubectl doesn't work, it's time for some Linux debugging! SSH to the control plane node and run:
$ ps aux | grep kube
This will show you if core components such as the kublet, kube-apiserver, kube-scheduler are up and running
$ ps aux | grep kube
This will show you if core components such as the kublet, kube-apiserver, kube-scheduler are up and running
After 16 episodes of #Klustered and 35 broken @kubernetesio clusters, here’s my top tips for anyone looking to sit their CKA, CKAD, or anyone operating Kubernetes.
If you don’t have any API server, it’s always one of three things.
1. You’ve not exported KUBECONFIG
2. Your KUBECONFIG has the wrong URL for the API server
3. Your static manifests, /etc/kubernetes/manifests, need fixed.
1. You’ve not exported KUBECONFIG
2. Your KUBECONFIG has the wrong URL for the API server
3. Your static manifests, /etc/kubernetes/manifests, need fixed.
The first two are easy fixes and the third is a rabbit hole of potential problems. As we’re all working with Kubeadm clusters these days, you can expect the static pod directory to contain manifests for the API server, etcd, controller managers, and your scheduler.
