Kubernetes
Image Management Tool -- Harbor
· ☕ 5 min read
1. Requirements for Building Harbor Harbor hardware requirements: CPU, at least 2 cores, 4 cores is better Mem, at least 4 GB, 8 GB is better Disk, at least 40 GB, 160 GB is better Docker version requirements: 17.06.0 or later To build Harbor on Kubernetes, you can refer to the documentation, Building Harbor with Helm.

Using emptyDir, hostPath, and localVolume in Kubernetes
· ☕ 4 min read
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.

Kubernetes Cluster Operations in Practice
· ☕ 11 min read
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.

Installing a Kubernetes Cluster with Kubeadm
· ☕ 4 min read
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

Kubernetes Complex Stateful Application Management Framework -- Operator
· ☕ 5 min read
1. Origins Originally, two CoreOS employees, in order to make deploying etcd clusters easier, bound corresponding logical operations to the create, delete, and update events of the etcdCluster object, using Kubernetes to automate etcd cluster management. A few months later, at a KubeCon conference, they shared this approach, which they called Operator, and it received a strong response from the community.