What is the CrashLoopBackOff status? A CrashLoopBackoff status within Kubernetes just means that a pod isn’t able to start or is failing over and over
Kubectl and kubens can easily be installed on any platform. Some features include adding aliases for insanely large cluster are namespace names. This means “denver-colordo-central-cluster”
This project boosts around kubectl 146 plugins and you can easily just write your own if there is something that you want to add yourself.
In the early days of running Kubernetes on premise we would get a user who would complain about ‘intermittent kubectl errors’. Typically this will be
This story starts when I noticed that nodes where going into a ‘NotReady’ status in a cluster. One ‘NotReady’ node was drained and rebooted only
While helping troubleshoot a issue in WordPress’s Woocommerce store front I noticed that orders with multiple shipping labels when purchased started failing the normal order
I found this site online and thought it was too good not to share. There are lots of interesting failures and postmortems within production Kubernetes
I wrote this little Ansible script from scratch in order to backup 3 X network interface configurations from CentOS 6 Transcoders and move them over
What you will need before you begin. A copy of the Finnix ISO You will need to install Virtualbox You will need your copy of
I was recently tasked with helping the the network team double check their ACLs so I built the following small script to meet the task.