From Kubernetes source: Limits and requests for memory are measured in bytes. You can express memory as a plain integer or as a fixed-point integer using one of these suffixes: E, P, T, G, M, K. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki. For example, the following represent roughly … Read more
One way would be kubectl delete -f <filename> but it implies few things: The resources were first created. It simply removes all of those, if you really want to “revert to the previous state” I’m not sure there are built-in tools in Kubernetes to do that (so you really would restore from a backup, if … Read more
create labels for the nodes: kubectl label node <nodename> <labelname>=allow delete above labels from its respecitve nodes: kubectl label node <nodename> <labelname>-
You are doing the correct action; traditionally the scale verb is applied just to the resource name, as in kubectl scale deploy my-awesome-deployment –replicas=0, which removes the need to always point at the specific file that describes that deployment, but there’s nothing wrong (that I know of) with using the file if that is more … Read more
kubectl version also shows the apiserver version. For example, this is the output when I run it: $ kubectl version Client Version: version.Info{Major:”1″, Minor:”2″, GitVersion:”v1.2.4″, GitCommit:”3eed1e3be6848b877ff80a93da3785d9034d0a4f”, GitTreeState:”clean”} Server Version: version.Info{Major:”1″, Minor:”2″, GitVersion:”v1.2.4″, GitCommit:”3eed1e3be6848b877ff80a93da3785d9034d0a4f”, GitTreeState:”clean”} The second line (“Server Version”) contains the apiserver version. There isn’t a way to get the master’s kubelet version if it … Read more
In Helm v3, the release name is now mandatory as part of the commmand, see helm install –help: Usage: helm install [NAME] [CHART] [flags] Your command should be: helm install my-nginx stable/nginx-ingress Furthermore, Helm will not auto-generate names for releases anymore. If you want the “old behavior”, you can use the –generate-name flag. e.g: helm … Read more
In a cluster best practices are to gather all logs in a single point through an aggregator and analyze them with a dedicated tool. For that reason in K8S, log command is quite basic. Anyway kubectl logs -h shows some options useful for you: # Display only the most recent 20 lines of output in … Read more
Yes, a regular pod can use a persistent volume. However, sometimes you have multiple pods that logically form a “group”. Examples of this would be database replicas, ZooKeeper hosts, Kafka nodes, etc. In all of these cases there’s a bunch of servers and they work together and talk to each other. What’s special about them … Read more
Do this: export KUBECONFIG=~/.kube/config:~/someotherconfig kubectl config view –flatten You can then pipe that out to a new file if needed.
This happens when persistent volume is protected. You should be able to cross verify this: Command: kubectl describe pvc PVC_NAME | grep Finalizers Output: Finalizers: [kubernetes.io/pvc-protection] You can fix this by setting finalizers to null using kubectl patch: kubectl patch pvc PVC_NAME -p ‘{“metadata”:{“finalizers”: []}}’ –type=merge Ref; Storage Object in Use Protection