When a namespace stucks in “terminating” state you have manually solve the blocking conditions. At first check the namespace: When the monitoring or metrics is broken there is similar message: Check the metrics.k8s.io apiservice: If there are missing endpoints or other error which caused the “AVAILABLE” field set to False, you need to deal it.… Read More: Kubernetes tips #2 – force-remove namespace »
If you want to check the actual usage of the PVCs, you can do it easily with kubedf . It requires the “jq” tool, which you can install by your package manager. (Eg.: apt install jq) Save the script into file called kubedf and set the execute right. kubectl proxy is required to be running.… Read More: Kubernetes tips #1 – kubedf »
” Kubernetes Dashboard is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage applications running in the cluster and troubleshoot them, as well as manage the cluster itself. “ Install and setup MetalLB For installing the Dashboard we need the installed Metrics server. Additionaly we need a load balancer. In cloud… Read More: Kubernetes #3 – MetalLB and Dashboard »
Note: This post was updated to actual (0.3.6) version of Kubernetes Metrics Server at 2020.06.10. For using kubectl top command we need metrics server, formally called Heapster. You can find the Kubernetes Metrics server at github: https://github.com/kubernetes-sigs/metrics-serverDocumentation: https://kubernetes.io/docs/tasks/debug-application-cluster/resource-metrics-pipeline You can check the versions at https://github.com/kubernetes-sigs/metrics-server/releases . To innstall the version 0.3.6 execute the following command:… Read More: Kubernetes #2 – Metrics Server »
This is a first attempt to create a clustered/cloud application on virtual machines running on bare metal(s). Host machine may be any Linux distribution which supports KVM. I used Linux Mint 18 in this case as KVM host. You can use more physical machines with oVirt or other virtualization technology. On virtual machines (VMs) was… Read More: Kubernetes #1 – Basic install »