1. Pulling images with docker pull When you pull an image with docker pull {IMAGE_NAME}, there are two cases: The IMAGE_NAME prefix points to a registry Docker recognizes IMAGE_NAME as an image provided by the specified repository. For example, for myregistry.io/space1/image1:latest, Docker requests the image data from the server that myregistry.

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.

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. The main and init Functions A package can contain multiple init functions, but it must contain exactly one main function. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 package main import ( "fmt" ) func init() { fmt.

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.