Author: Du Jun Publisher: Publishing House of Electronics Industry Published: 2019-10 ISBN: 9787121373398 Notes: Networking is one of the harder parts of Kubernetes to master. Network failures directly affect the running workloads, and they are usually very urgent problems. Networking knowledge is also lower-level than application development, with many details that require long-term accumulation.

1. RESTful Requests 1 curl -X POST --data 'keyword=value' http://domain.com/mypath/ After -X you can also use DELETE, PUT, and so on. 2. Adding Headers 1 curl -H 'Content-Type:application/json' -H 'Authorization: bearer MyToken' http://domain.com/mypath/ 3. Basic Authentication 1 curl -u username:password http://domain.com/mypath/ 4. Download and Execute 1 curl -sSL http://domain.com/my.sh | bash 5.

Usually, running a command of the form export http_proxy/https_proxy on the host is enough to set a Proxy. However, settings on the host do not take effect inside containers. Below are several configuration approaches. 1. Configure Docker’s proxy - Node level Configure this on the node that needs the Proxy.

1. About DNS 1.1 What the DNS Service Is For DNS provides a mapping service from domain names to IPs. For example, you type https://www.chenshaowen.com into a browser to open a page, but the data link communicates over IP and cannot recognize www.chenshaowen.com. This is where a DNS lookup comes in: the input is www.

The official Helm repo https://charts.helm.sh/stable is unreachable from some machines in China, so you need to configure a mirror. 1. Official Repo 1 helm repo add stable https://charts.helm.sh/stable 2. Git Pages Mirror 1 helm repo add stable https://burdenbear.github.io/kube-charts-mirror/ See kube-charts-mirror for a reference on building a self-hosted, self-controlled mirror.