K 8 sはLinuxONE上に構築(一)

一、紹介
Kubernetesは人気のある技術であり、すでにオープンソースのPASS管理プラットフォームの標準となっている.K 8 Sプラットフォームの主流を構築するには2つの方法があります.

第1種はバイナリベースの構築であり、一歩一歩の構築によってK 8 Sの各サービスに対する理解を深めることができる.

公式推奨の自動化配備ツールkubeadmは今回、公式推奨のKubeadmの構築方法を使用し、kubedmはK 8 S自身のサービスをK 8 S自身のpodによって実行するほか、事前の基礎サービスはsystemサービスで実行する.masterノードインストールコンポーネント:docker、kubelet、kubeadmローカルシステムベースサービス実行kube-proxyは、動的にk 8 sで管理可能なpodapi-server、kube-controller、etcdであり、podnodeノードコンポーネントdocker、kubeletローカルシステムベースサービス実行kube-proxyは、動的にk 8 sで管理可能なpodflannelは、動的にk 8 sで管理可能なpod 2、インストール1.環境

システムバージョン
IPアドレス
ホスト名
ubuntu1~18.04.1
172.16.35.140
master
ubuntu1~18.04.1
woker-1
2.dockerインストールベースのパッケージをインストールする

apt-get install \
    apt-transport-https \
    ca-certificates \
    curl \
    gnupg-agent \
    software-properties-common

公式のkeyを追加

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -

dockerソースの追加

sudo add-apt-repository \
 "deb [arch=s390x] https://download.docker.com/linux/ubuntu \
 $(lsb_release -cs) \
 stable"

dockerのインストール

 apt-get update;apt-get install docker-ce

3、クbelet、クbeadmをインストールしてソースを追加する

apt-get update && apt-get install -y apt-transport-https
curl https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | apt-key add - 
cat </etc/apt/sources.list.d/kubernetes.list
deb https://mirrors.aliyun.com/kubernetes/apt/ kubernetes-xenial main
EOF  
apt-get update
apt-get install -y kubelet kubeadm kubec

4、kubeadmを利用して環境を初期化する前に、以下の準備を自分で行う必要があります.
初期化環境:1、ホスト名通信2、時間同期3、ファイアウォールクローズ4、swapoff-a&&sysctl-w vm.swappiness=0 && sysctl -w net.ipv4.ip_forward=1\echo 1 >/proc/sys/net/bridge/bridge-nf-call-ip6tables\echo 1 >/proc/sys/net/bridge/bridge-nf-call-iptables
kubeadmに必要なベースのdockerイメージを表示

root@master:/etc/apt# kubeadm config images list
W0321 08:51:12.828065   19587 version.go:101] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://dl.k8s.io/release/stable-1.txt: dial tcp: lookup dl.k8s.io on 127.0.0.53:53: server misbehaving
W0321 08:51:12.828143   19587 version.go:102] falling back to the local client version: v1.17.4
W0321 08:51:12.828250   19587 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0321 08:51:12.828275   19587 validation.go:28] Cannot validate kubelet config - no validator is available
k8s.gcr.io/kube-apiserver:v1.17.4
k8s.gcr.io/kube-controller-manager:v1.17.4
k8s.gcr.io/kube-scheduler:v1.17.4
k8s.gcr.io/kube-proxy:v1.17.4
k8s.gcr.io/pause:3.1
k8s.gcr.io/etcd:3.4.3-0
k8s.gcr.io/coredns:1.6.5

説明できない要因のため、k 8 sに直接アクセスすることはできません.gcr.ioだから私たちは自分でこのいくつかのミラーをダウンロードする必要があります.私はすでにミラーを私のdocker hubにアップロードしました.みんなは自分でpullすることができます.

 docker pull  erickshi/kube-apiserver-s390x:v1.17.4
 docker pull  erickshi/kube-scheduler-s390x:v1.17.4
 docker pull  erickshi/kube-controller-manager-s390x:v1.17.4 
 docker pull  erickshi/pause-s390x:3.1 
 docker pull  erickshi/coredns:s390x-1.6.5
 docker pull  erickshi/etcd:3.4.3-0
 docker pull  erickshi/pause:3.1

ダウンロードが終わったら、kubeadmがダウンロードするので、私たちと同じ名前に変更する必要があります.

 docker tag erickshi/kube-apiserver-s390x:v1.17.4 k8s.gcr.io/kube-apiserver:v1.17.4
 docker tag erickshi/kube-scheduler-s390x:v1.17.4 k8s.gcr.io/kube-scheduler:v1.17.4
 docker tag erickshi/kube-controller-manager-s390x:v1.17.4 k8s.gcr.io/kube-controller-manager:v1.17.4
docker tag erickshi/pause-s390x:3.1 k8s.gcr.io/pause:3.1
docker tag erickshi/etcd-s390x:3.4.3-0 k8s.gcr.io/etcd:3.4.3-0
docker tags erickshi/coredns:s390x-1.6.5 k8s.gcr.io/coredns:1.6.5
docker tag erickshi/coredns:s390x-1.6.5 k8s.gcr.io/coredns:1.6.5

次に、クラスタを正式に初期化します.

root@master:~#  kubeadm init --kubernetes-version=v1.17.4  --service-cidr=10.96.0.0/12
W0321 09:57:23.233367    9597 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0321 09:57:23.233401    9597 validation.go:28] Cannot validate kubelet config - no validator is available
[init] Using Kubernetes version: v1.17.4
[preflight] Running pre-flight checks
    [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.16.35.140]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [master localhost] and IPs [172.16.35.140 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [master localhost] and IPs [172.16.35.140 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
W0321 09:57:32.529825    9597 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
[control-plane] Creating static Pod manifest for "kube-scheduler"
W0321 09:57:32.530693    9597 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 12.001699 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.17" in namespace kube-system with the configuration for the kubelets in the cluster
[upload-certs] Skipping phase. Please see --upload-certs
[mark-control-plane] Marking the node master as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: rp81u6.x7rky04rds2knxb8
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
[bootstrap-token] Creating the "cluster-info" ConfigMap in the "kube-public" namespace
[kubelet-finalize] Updating "/etc/kubernetes/kubelet.conf" to point to a rotatable kubelet client certificate and key
[addons] Applied essential addon: CoreDNS
[addons] Applied essential addon: kube-proxy

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

  mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 172.16.35.140:6443 --token g6dykf.ac2mtjv9y4bfk4ve \
    --discovery-token-ca-cert-hash sha256:f868a8621420b253a7f6de4cae65c17c001c3ecb0740b549f9d0adca48b77f06

初期化に成功したことがわかります.ユーザーの認証ファイルを対応する場所にコピーする必要があります.

 mkdir -p $HOME/.kube
  sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
  sudo chown $(id -u):$(id -g) $HOME/.kube/config

次に、現在の環境を表示します.

root@master:/etc/apt# kubectl  get node
NAME     STATUS     ROLES    AGE    VERSION
master   NotReady   master   159m   v1.17.4
root@master:/etc/apt# kubectl  get cs
NAME                 STATUS    MESSAGE             ERROR
scheduler            Healthy   ok
controller-manager   Healthy   ok
etcd-0               Healthy   {"health":"true"}

次に、k 8 sにおけるトガンのサービスを見てみましょう.

root@master:/etc/apt# kubectl  get pod --all-namespaces
NAMESPACE     NAME                             READY   STATUS    RESTARTS   AGE
kube-system   coredns-6955765f44-gfjk2         0/1     Pending   0          159m
kube-system   coredns-6955765f44-l25vq         0/1     Pending   0          159m
kube-system   etcd-master                      1/1     Running   0          159m
kube-system   kube-apiserver-master            1/1     Running   0          159m
kube-system   kube-controller-manager-master   1/1     Running   0          159m
kube-system   kube-proxy-xfw6v                 1/1     Running   0          159m
kube-system   kube-scheduler-master            1/1     Running   0          159m

次にflanalネットワークをインストールしてまずflannel imageをダウンロードします

wget https://github.com/coreos/flannel/releases/download/v0.12.0/flanneld-v0.12.0-s390x.docker
    docker load  < flanneld-v0.12.0-s390x.docker

  kubectl apply   -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml

現在のnodeの表示

root@master:~# kubectl  get node
NAME     STATUS   ROLES    AGE     VERSION
master   Ready    master   2m31s   v1.17.4
root@master:~#
root@master:/tmp# kubectl  get pod --all-namespaces
NAMESPACE     NAME                             READY   STATUS    RESTARTS   AGE
kube-system   coredns-6955765f44-gzd5g         1/1     Running   0          99m
kube-system   coredns-6955765f44-qjzfd         1/1     Running   0          99m
kube-system   etcd-master                      1/1     Running   0          99m
kube-system   kube-apiserver-master            1/1     Running   0          99m
kube-system   kube-controller-manager-master   1/1     Running   0          99m
kube-system   kube-flannel-ds-s390x-mnqs5      1/1     Running   0          98m
kube-system   kube-proxy-jstmj                 1/1     Running   0          99m
kube-system   kube-scheduler-master            1/1     Running   0          99m

ノードのインストール
クベドでマスターに加える

root@node:~# kubeadm join 172.16.35.140:6443 --token g6dykf.ac2mtjv9y4bfk4ve     --discovery-token-ca-cert-hash sha256:f868a8621420b253a7f6de4cae65c17c001c3ecb0740b549f9d0adca48b77f06 -v=15
W0326 08:12:42.444748   10170 join.go:346] [preflight] WARNING: JoinControlPane.controlPlane settings will be ignored when control-plane flag is not set.
I0326 08:12:42.444787   10170 join.go:371] [preflight] found NodeName empty; using OS hostname as NodeName
I0326 08:12:42.444808   10170 initconfiguration.go:103] detected and using CRI socket: /var/run/dockershim.sock
[preflight] Running pre-flight checks
I0326 08:12:42.444861   10170 preflight.go:90] [preflight] Running general checks
I0326 08:12:42.444894   10170 checks.go:249] validating the existence and emptiness of directory /etc/kubernetes/manifests
I0326 08:12:42.444929   10170 checks.go:286] validating the existence of file /etc/kubernetes/kubelet.conf
.......
....:
........
{"machineID":"db770448baee44b4b07b748869a6f769","systemUUID":"db770448baee44b4b07b748869a6f769","bootID":"0112b3ec-f380-42d1-a5af-c459f7731c1d","kernelVersion":"4.15.0-91-generic","osImage":"Ubuntu 18.04.4 LTS","containerRuntimeVersion":"docker://18.6.3","kubeletVersion":"v1.17.4","kubeProxyVersion":"v1.17.4","operatingSystem":"linux","architecture":"s390x"}}}

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

root@node:~#

マスターノードで現在のステータスを表示する

root@master:/tmp# kubectl  get node
NAME     STATUS     ROLES    AGE    VERSION
master   Ready      master   137m   v1.17.4
node     NotReady      10s    v1.17.4

現在のnodeノードにreadyがないのは、ネットワークがインストールされていないためです.次にネットワークnodeノードのインストールを開始するには、flanneld、pause、kube-proxyミラーも必要です.ここではインポート手順を省略します.

kubectl apply   -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml  

nodeステータスの再表示

root@master:~# kubectl  get node
NAME     STATUS   ROLES    AGE    VERSION
master   Ready    master   4h2m   v1.17.4
node     Ready       104m   v1.17.4

これでアプリケーションを導入できます!