I am using Kubernetes 1.15.3; the way different versions handle this may vary. 1. About Certificates A root certificate is self-signed A root certificate is issued by itself. Browsers have the CA certificates of common certificate vendors built in. That is why browsers trust the next-level certificates issued by those vendors.

With the Operator approach, Kubernetes functionality can be extended in a friendly way. Operator = CRD + Controller. First you generate the CRD from a yaml definition, then the Controller continuously watches the data in etcd and performs the corresponding actions. There is a lot of tedious and repetitive work involved in developing an Operator.

1. CNI Problems Error log 1 2 journalctl -u kubelet ...Unable to update cni config: No networks found in /etc/cni/net.d Because no CNI is installed, you need to remove --network-plugin=cni from the parameters in /var/lib/kubelet/kubeadm-flags.env. 1 2 cat /var/lib/kubelet/kubeadm-flags.env KUBELET_KUBEADM_ARGS="--cgroup-driver=systemd --pod-infra-container-image=k8s.gcr.io/pause:3.1" 2. Node NotReady There can be many reasons for a node being NotReady.

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.

Prerequisites: (1) Helm is already installed, see Installing Helm; (2) the cluster has default dynamic storage available, see Providing PV Dynamic Storage with StorageClass 1. Installing Ingress with Helm Ingress consists of two parts: Ingress and the Ingress Controller. In Kubernetes, the Ingress object describes routing rules; the Ingress Controller interacts with the Apiserver and writes the Ingress rules into the Nginx Pod.