Earlier, in Kubernetes Volumes, we got some understanding of Volumes. This post focuses on practice, learning how to use the three local storage options: emptydir, hostpath, and localvolume. 1. Basic Properties of a PV 1.1 PV Lifecycle PV states: Available: available, not yet bound by any PVC Bound: already bound to a PVC Released: the PVC was deleted, but the resource has not yet been reclaimed Failed: automatic reclamation failed 1.

Compiled from the “Development Tips” series, gathering the common problems and solutions from day-to-day Kubernetes cluster operations. 1. Configuring Multiple Clusters with Kubectl When doing Kubernetes-related development you usually end up managing several clusters. Kubectl provides multi-cluster context management. Kubectl’s configuration usually lives in $HOME/.kube/config or /etc/kubernetes/admin.conf. Log into the machine, look at the cluster configuration, and edit it using the format below.

1. Cluster Planning Prepare three hosts: one Master and two Nodes. Operating system: CentOS 7 Specs: 2 Core 4 GB Docker version: 18.06.3 Kubernetes version: 1.15.3 If you are using a purchased cloud host, open the following ports: 1 2 3 4 5 6 7 8 9 10 11 12

1. Different Kinds of Storage 1.1 File Storage File storage is storage based on files. When accessing data, you need to provide the corresponding lookup path. It is suitable for services such as FTP and NFS. 1.2 Block Storage Block storage splits data into blocks and stores each part separately. When accessing data, the underlying storage software reassembles these scattered pieces.

1. Docker Storage Volumes 1.2 Volumes in Docker A Docker volume mounts a host directory into a container. Files modified inside the container are persisted to the host. Even if the container is deleted, the files on the host are retained. Docker uses /var/lib/docker/volumes/ to store container volumes. List local volumes: