摘要:執(zhí)行查看所狀態(tài),已經(jīng)都部署是可選組件,因為,實在不好用,功能太弱了。使用做為的后端存儲,開始部署使用到的鏡像最后確認所有的都處于狀態(tài),打開集群的使用統(tǒng)計會以儀表盤的形式顯示出來本涉及到安裝的鏡像鏈接密碼
壞境說明:
192.168.111.117 huaicong-1 master 192.168.111.123 huaicong-2 slave 192.168.111.184 huaicong-3 slave配置互信
生成ssh 密鑰對 [root@huaicong-1 ~]# ssh-keygen 把本地的ssh公鑰文件安裝到遠程主機對應的賬戶 [root@huaicong-1 ~]# ssh-copy-id huaicong-1 [root@huaicong-1 ~]# ssh-copy-id huaicong-2 [root@huaicong-1 ~]# ssh-copy-id huaicong-3關(guān)閉防火墻&&關(guān)閉selinux
[root@huaicong-1 ~]# systemctl stop firewalld [root@huaicong-1 ~]# systemctl disable firewalld [root@huaicong-1 ~]# cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of three two values: # targeted - Targeted processes are protected, # minimum - Modification of targeted policy. Only selected processes are protected. # mls - Multi Level Security protection. SELINUXTYPE=targeted開始安裝 所有節(jié)點操作
鏈接:https://pan.baidu.com/s/1ExMT... 密碼:otpq
下載相關(guān)rpm 包還有相關(guān) docker images. 并解壓[root@huaicong-1 ~]# tar -zxvf k8s_images.tar.gz安裝docker-ce,解決依賴
[root@huaicong-1 k8s_images]# rpm -ivh libtool-ltdl-2.4.2-22.el7_3.x86_64.rpm libxml2-python-2.9.1-6.el7_2.3.x86_64.rpm libseccomp-2.3.1-3.el7.x86_64.rpm [root@huaicong-1 k8s_images]# rpm -ivh docker-ce-selinux-17.03.2.ce-1.el7.centos.noarch.rpm [root@huaicong-1 k8s_images]# rpm -ivh docker-ce-17.03.2.ce-1.el7.centos.x86_64.rpm修改docker的鏡像源為國內(nèi)的daocloud的。
curl -sSL https://get.daocloud.io/daotools/set_mirror.sh | sh -s http://a58c8480.m.daocloud.io啟動docker,并設置開機啟動
[root@huaicong-1 ~]# systemctl start docker;systemctl enable docker配置系統(tǒng)路由參數(shù),防止kubeadm報路由警告
echo " net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 " >> /etc/sysctl.conf sysctl -p安裝kubadm kubelet kubectl
[root@huaicong-1 k8s_images]# rpm -ivh kubectl-1.9.0-0.x86_64.rpm kubeadm-1.9.0-0.x86_64.rpm kubelet-1.9.9-9.x86_64.rpm kubernetes-cni-0.6.0-0.x86_64.rpm socat-1.7.3.2-2.el7.x86_64.rpm加載鏡像
[root@huaicong-1 ~]# cd k8s_images/docker_images/ [root@huaicong-1 docker_images]# ll total 999696 -rw-r--r-- 1 root root 192984064 Dec 26 11:32 etcd-amd64_v3.1.10.tar -rw-r--r-- 1 root root 52185600 Dec 27 20:36 flannel:v0.9.1-amd64.tar -rw-r--r-- 1 root root 41241088 Dec 27 20:34 k8s-dns-dnsmasq-nanny-amd64_v1.14.7.tar -rw-r--r-- 1 root root 50545152 Dec 27 23:02 k8s-dns-kube-dns-amd64_1.14.7.tar -rw-r--r-- 1 root root 42302976 Dec 27 22:59 k8s-dns-sidecar-amd64_1.14.7.tar -rw-r--r-- 1 root root 210598400 Dec 26 11:28 kube-apiserver-amd64_v1.9.0.tar -rw-r--r-- 1 root root 137975296 Dec 26 11:30 kube-controller-manager-amd64_v1.9.0.tar -rw-r--r-- 1 root root 110955520 Dec 29 13:13 kube-proxy-amd64_v1.9.0.tar -rw-r--r-- 1 root root 121195008 Jan 1 20:24 kubernetes-dashboard_v1.8.1.tar -rw-r--r-- 1 root root 62920704 Dec 26 11:30 kube-scheduler-amd64_v1.9.0.tar -rw-r--r-- 1 root root 765440 Dec 27 20:32 pause-amd64_3.0.tar [root@huaicong-1 docker_images]# for image in `ls -l . |awk "{print $9}"`;do echo "$image is loading"&&docker load < ${image};donemaster 節(jié)點操作
#啟動kubelet [root@huaicong-1 ~]# systemctl start kubelet&& systemctl enable kubelet開始初始化master節(jié)點
kubernetes 默認支持多重網(wǎng)絡插件如flannel、weave、calico,這里使用flannel,就必須設置--pod-network-cidr 參數(shù),
[root@huaicong-1 ~]# kubeadm init --kubernetes-version=v1.9.0 --pod-network-cidr=10.224.0.0/16
Jan 20 15:22:53 huaicong-1 kubelet: E0120 15:22:53.551735 24627 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.111.117:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dhuaicong-1.novalocal&limit=500&resourceVersion=0: dial tcp 192.168.111.117:6443: getsockopt: connection refused Jan 20 15:22:53 huaicong-1 kubelet: E0120 15:22:53.551845 24627 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:474: Failed to list *v1.Node: Get https://192.168.111.117:6443/api/v1/nodes?fieldSelector=metadata.name%3Dhuaicong-1.novalocal&limit=500&resourceVersion=0: dial tcp 192.168.111.117:6443: getsockopt: connection refused Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.557159 24627 kubelet_network.go:139] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth" Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.557178 24627 kubelet.go:571] Hairpin mode set to "hairpin-veth" Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.557212 24627 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.557240 24627 client.go:80] Connecting to docker on unix:///var/run/docker.sock Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.557249 24627 client.go:109] Start docker client with request timeout=2m0s Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.559152 24627 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d Jan 20 15:22:53 huaicong-1 kubelet: W0120 15:22:53.581459 24627 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.581544 24627 docker_service.go:232] Docker cri networking managed by cni Jan 20 15:22:53 huaicong-1 kubelet: I0120 15:22:53.599739 24627 docker_service.go:237] Docker Info: &{ID:FMCL:A6AR:LAHK:SS2I:2SJI:ZY73:HYS4:DRRU:AJI4:JOQM:L5XK:ZGLK Containers:0 ContainersRunning:0 ContainersPaused:0 ContainersStopped:0 Images:11 Driver:overlay DriverStatus:[[Backing Filesystem xfs] [Supports d_type true]] SystemStatus:[] Plugins:{Volume:[local] Network:[bridge host macvlan null overlay] Authorization:[] Log:[]} MemoryLimit:true SwapLimit:true KernelMemory:true CPUCfsPeriod:true CPUCfsQuota:true CPUShares:true CPUSet:true IPv4Forwarding:true BridgeNfIptables:true BridgeNfIP6tables:true Debug:false NFd:16 OomKillDisable:true NGoroutines:22 SystemTime:2018-01-20T15:22:53.586684761+08:00 LoggingDriver:json-file CgroupDriver:cgroupfs NEventsListener:0 KernelVersion:3.10.0-514.el7.x86_64 OperatingSystem:CentOS Linux 7 (Core) OSType:linux Architecture:x86_64 IndexServerAddress:https://index.docker.io/v1/ RegistryConfig:0xc420e63960 NCPU:2 MemTotal:3975086080 GenericResources:[] DockerRootDir:/var/lib/docker HTTPProxy: HTTPSProxy: NoProxy: Name:huaicong-1.novalocal Labels:[] ExperimentalBuild:false ServerVersion:17.03.2-ce ClusterStore: ClusterAdvertise: Runtimes:map[runc:{Path:docker-runc Args:[]}] DefaultRuntime:runc Swarm:{NodeID: NodeAddr: LocalNodeState:inactive ControlAvailable:false Error: RemoteManagers:[] Nodes:0 Managers:0 Cluster:0xc4201cb400} LiveRestoreEnabled:false Isolation: InitBinary:docker-init ContainerdCommit:{ID:4ab9917febca54791c5f071a9d1f404867857fcc Expected:4ab9917febca54791c5f071a9d1f404867857fcc} RuncCommit:{ID:54296cf40ad8143b62dbcaa1d90e520a2136ddfe Expected:54296cf40ad8143b62dbcaa1d90e520a2136ddfe} InitCommit:{ID:949e6fa Expected:949e6fa} SecurityOptions:[name=seccomp,profile=default]} Jan 20 15:22:53 huaicong-1 kubelet: error: failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgroup driver: "systemd" is different from docker cgroup driver: "cgroupfs" Jan 20 15:22:53 huaicong-1 systemd: kubelet.service: main process exited, code=exited, status=1/FAILURE Jan 20 15:22:53 huaicong-1 systemd: Unit kubelet.service entered failed state. Jan 20 15:22:53 huaicong-1 systemd: kubelet.service failed.查看日志發(fā)現(xiàn)啟動不了
原來是kubelet 的cgroup dirver 與 docker的不一樣。docker默認使用cgroupfs,keubelet 默認使用systemd。
[root@huaicong-1 ~]# vim /etc/systemd/system/kubelet.service.d/10-kubeadm.conf [Service] Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf" Environment="KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests --allow-privileged=true" Environment="KUBELET_NETWORK_ARGS=--network-plugin=cni --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin" Environment="KUBELET_DNS_ARGS=--cluster-dns=10.96.0.10 --cluster-domain=cluster.local" Environment="KUBELET_AUTHZ_ARGS=--authorization-mode=Webhook --client-ca-file=/etc/kubernetes/pki/ca.crt" Environment="KUBELET_CADVISOR_ARGS=--cadvisor-port=0" Environment="KUBELET_CGROUP_ARGS=--cgroup-driver=cgroupfs" Environment="KUBELET_CERTIFICATE_ARGS=--rotate-certificates=true --cert-dir=/var/lib/kubelet/pki" ExecStart= ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_SYSTEM_PODS_ARGS $KUBELET_NETWORK_ARGS $KUBELET_DNS_ARGS $KUBELET_AUTHZ_ARGS $KUBELET_CADVISOR_ARGS $KUBELET_CGROUP_ARGS $KUBELET_CERTIFICATE_ARGS $KUBELET_EXTRA_ARGSdadmon-reload && systemctl restart kubelet
[root@huaicong-1 ~]# kubeadm init --kubernetes-version=v1.9.0 --pod-network-cidr=10.244.0.0/16 [init] Using Kubernetes version: v1.9.0 [init] Using Authorization modes: [Node RBAC] [preflight] Running pre-flight checks. [WARNING Hostname]: hostname "huaicong-1.novalocal" could not be reached [WARNING Hostname]: hostname "huaicong-1.novalocal" lookup huaicong-1.novalocal on 8.8.4.4:53: no such host [WARNING FileExisting-crictl]: crictl not found in system path [preflight] Starting the kubelet service [certificates] Generated ca certificate and key. [certificates] Generated apiserver certificate and key. [certificates] apiserver serving cert is signed for DNS names [huaicong-1.novalocal kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 192.168.111.117] [certificates] Generated apiserver-kubelet-client certificate and key. [certificates] Generated sa key and public key. [certificates] Generated front-proxy-ca certificate and key. [certificates] Generated front-proxy-client certificate and key. [certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki" [kubeconfig] Wrote KubeConfig file to disk: "admin.conf" [kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf" [kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf" [kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf" [controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml" [controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml" [controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml" [etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml" [init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests". [init] This might take a minute or longer if the control plane images have to be pulled. [apiclient] All control plane components are healthy after 30.001793 seconds [uploadconfig]?Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace [markmaster] Will mark node huaicong-1.novalocal as master by adding a label and a taint [markmaster] Master huaicong-1.novalocal tainted and labelled with key/value: node-role.kubernetes.io/master="" [bootstraptoken] Using token: 7529d9.235a9be16773cad7 [bootstraptoken] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials [bootstraptoken] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token [bootstraptoken] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster [bootstraptoken] Creating the "cluster-info" ConfigMap in the "kube-public" namespace [addons] Applied essential addon: kube-dns [addons] Applied essential addon: kube-proxy Your Kubernetes master 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/ You can now join any number of machines by running the following on each node as root: kubeadm join --token 7529d9.235a9be16773cad7 192.168.111.117:6443 --discovery-token-ca-cert-hash sha256:5cde22b6b719d1af19c711b87016163baafd38e5588786ebd4a2b975a07439fd
kubeadm join xxxx 可以保留下來,如果忘記了,可以通過kubeadm token list 獲取
[root@huaicong-1 k8s_images]# kubeadm token list TOKEN TTL EXPIRES USAGES DESCRIPTION EXTRA GROUPS 7529d9.235a9be16773cad7 21h 2018-01-21T16:00:46+08:00 authentication,signing The default bootstrap token generated by "kubeadm init". system:bootstrappers:kubeadm:default-node-token
按照上面提示,此時還不能用kubectl 控制集群。需要配置環(huán)境變量
mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
kubectl version測試
[root@huaicong-1 k8s_images]# kubectl version Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T20:55:30Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
安裝網(wǎng)絡,可用使用flannel、macvlan、calico、weave,這里我們使用flannel。
#下載此文件 wget https://raw.githubusercontent.com/coreos/flannel/v0.9.1/Documentation/kube-flannel.yml
或直接使用離線包里面的
若要修改網(wǎng)段,需要kubeadm –pod-network-cidr=和這里同步,修改network項。
vim kube-flannel.yml net-conf.json: | 64 { 65 "Network": "10.244.0.0/16", 66 "Backend": { 67 "Type": "vxlan" 68 } 69 }
執(zhí)行
kubectl create -f kube-flannel.yml
查看所pod狀態(tài),已經(jīng)都running
[root@huaicong-1 k8s_images]# kubectl get pod --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system etcd-huaicong-1.novalocal 1/1 Running 0 2h kube-system kube-apiserver-huaicong-1.novalocal 1/1 Running 0 2h kube-system kube-controller-manager-huaicong-1.novalocal 1/1 Running 0 2h kube-system kube-dns-6f4fd4bdf-j9gd4 3/3 Running 0 2h kube-system kube-flannel-ds-jb66l 1/1 Running 0 25s kube-system kube-proxy-clhpp 1/1 Running 0 2h kube-system kube-scheduler-huaicong-1.novalocal 1/1 Running 0 2h部署kubernetes-dashboard
kubernetes-dashboard是可選組件,因為,實在不好用,功能太弱了。
建議在部署master時一起把kubernetes-dashboard一起部署了,不然在node節(jié)點加入集群后,kubernetes-dashboard會被kube-scheduler調(diào)度node節(jié)點上,這樣根kube-apiserver通信需要額外配置。
下載kubernetes-dashboard的配置文件或直接使用離線包里面的kubernetes-dashboard.yaml
[root@huaicong-1 k8s_images]# kubectl create -f kubernetes-dashboard.yaml [root@huaicong-1 k8s_images]# kubectl get pod --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system etcd-huaicong-1.novalocal 1/1 Running 0 2h kube-system kube-apiserver-huaicong-1.novalocal 1/1 Running 0 2h kube-system kube-controller-manager-huaicong-1.novalocal 1/1 Running 0 2h kube-system kube-dns-6f4fd4bdf-j9gd4 3/3 Running 0 2h kube-system kube-flannel-ds-jb66l 1/1 Running 0 25m kube-system kube-proxy-clhpp 1/1 Running 0 2h kube-system kube-scheduler-huaicong-1.novalocal 1/1 Running 0 2h kube-system kubernetes-dashboard-58f5cb49c-m4f5z 1/1 Running 0 27snode節(jié)點操作
修改kubelet配置文件根上面有一將cgroup的driver由systemd改為cgroupfs
vim /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
Environment=”KUBELET_CGROUP_ARGS=–cgroup-driver=cgroupfs”
systemctl daemon-reload systemctl enable kubelet&&systemctl restart kubelet使用剛剛執(zhí)行kubeadm后的kubeadm join –xxx
kubeadm join --token 6c5a50.4fc04fd2f05054ed 192.168.111.123:6443 --discovery-token-ca-cert-hash sha256:fb12670b0c600f310f6d18dae6b19ce7145069afd613dea46bf15be6611306e4在master節(jié)點上check一下
[root@huaicong-2 ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION huaicong-2.novalocal Ready master 14h v1.9.0 huaicong-3.novalocal Ready測試集群25s v1.9.0
在master節(jié)點上發(fā)起個創(chuàng)建應用請求
這里我們創(chuàng)建個名為httpd-app的應用,鏡像為httpd,有兩個副本pod
kubectl run httpd-app --image=httpd --replicas=2
[root@huaicong-2 ~]# kubectl get deployment NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE httpd-app 2 2 2 2 13m [root@huaicong-2 ~]#
[root@huaicong-2 ~]# kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE httpd-app-5fbccd7c6c-bbl2c 1/1 Running 0 14m 10.244.1.3 huaicong-3.novalocal httpd-app-5fbccd7c6c-ksw9b 1/1 Running 0 14m 10.244.1.4 huaicong-3.novalocal [root@huaicong-2 ~]#因為創(chuàng)建的資源不是service所以不會調(diào)用kube-proxy
直接訪問測試
[root@huaicong-2 ~]# curl http://10.244.1.3It works!
[root@huaicong-2 ~]# curl http://10.244.1.4It works!
[root@huaicong-2 ~]#
[root@huaicong-2 ~]# kubectl delete deployment httpd-app [root@huaicong-2 ~]# kubectl get pods NAME READY STATUS RESTARTS AGE httpd-app-5fbccd7c6c-bbl2c 0/1 Terminating 0 56m httpd-app-5fbccd7c6c-ksw9b 0/1 Terminating 0 56m至此kubernetes基本集群安裝完成。 heapster插件部署
下面安裝Heapster為集群添加使用統(tǒng)計和監(jiān)控功能,為Dashboard添加儀表盤。 使用InfluxDB做為Heapster的后端存儲,開始部署:
使用到的鏡像
mkdir -p ~/k8s/heapster cd ~/k8s/heapster wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/grafana.yaml wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/rbac/heapster-rbac.yaml wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/heapster.yaml wget https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/influxdb.yaml kubectl create -f ./
最后確認所有的pod都處于running狀態(tài),打開Dashboard,集群的使用統(tǒng)計會以儀表盤的形式顯示出來
本涉及到安裝的鏡像gcr.io/google_containers/kube-proxy-amd64:v1.9.0 gcr.io/google_containers/kube-apiserver-amd64:v1.9.0 gcr.io/google_containers/kube-controller-manager-amd64:v1.9.0 gcr.io/google_containers/kube-scheduler-amd64:v1.9.0 quay.io/coreos/flannel:v0.9.1-amd64 gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.7 gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.7 gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.7 gcr.io/google_containers/etcd-amd64:3.1.10 gcr.io/google_containers/pause-amd64:3.0 gcr.io/google_containers/kubernetes-dashboard-amd64:v1.8.1 gcr.io/google_containers/heapster-influxdb-amd64:v1.3.3 gcr.io/google_containers/heapster-grafana-amd64:v4.4.3 gcr.io/google_containers/heapster-amd64:v1.4.2
鏈接:https://pan.baidu.com/s/1ExMT... 密碼:otpq
文章版權(quán)歸作者所有,未經(jīng)允許請勿轉(zhuǎn)載,若此文章存在違規(guī)行為,您可以聯(lián)系管理員刪除。
轉(zhuǎn)載請注明本文地址:http://specialneedsforspecialkids.com/yun/32646.html
摘要:年月日,發(fā)布版本,本次版本更新帶來了全新的應用市場交付體驗,并對源碼類服務的運行機制架構(gòu)服務管理等方面做了大量優(yōu)化。發(fā)布社區(qū)公開應用。我們正在進行的是將應用轉(zhuǎn)化為應用存放于應用市場中供用戶直接安裝使用。 2019年7月8日,Rainbond發(fā)布5.1.5版本,本次版本更新帶來了全新的應用市場交付Pipeline體驗,并對源碼類服務的運行機制、ServiceMesh架構(gòu)、服務管理等方面做...
摘要:去年宣布的現(xiàn)在為云原生計算帶來了好消息它提供了基于的完整邊緣計算解決方案,具有獨立的云和邊緣核心模塊。這將有助于邊緣云的行為與云集群完全相同。它是一個套接字客戶端,負責與進行邊緣計算交互。 作者:Sanil Kumar D(華為),Jun Du(華為) KubeEdge成為第一個Kubernetes原生邊緣計算平臺,Edge和云組件現(xiàn)已開源! 開源邊緣計算正在經(jīng)歷其業(yè)界最具活力的發(fā)展階...
摘要:去年宣布的現(xiàn)在為云原生計算帶來了好消息它提供了基于的完整邊緣計算解決方案,具有獨立的云和邊緣核心模塊。這將有助于邊緣云的行為與云集群完全相同。它是一個套接字客戶端,負責與進行邊緣計算交互。 作者:Sanil Kumar D(華為),Jun Du(華為) KubeEdge成為第一個Kubernetes原生邊緣計算平臺,Edge和云組件現(xiàn)已開源! 開源邊緣計算正在經(jīng)歷其業(yè)界最具活力的發(fā)展階...
摘要:去年宣布的現(xiàn)在為云原生計算帶來了好消息它提供了基于的完整邊緣計算解決方案,具有獨立的云和邊緣核心模塊。這將有助于邊緣云的行為與云集群完全相同。它是一個套接字客戶端,負責與進行邊緣計算交互。 作者:Sanil Kumar D(華為),Jun Du(華為) KubeEdge成為第一個Kubernetes原生邊緣計算平臺,Edge和云組件現(xiàn)已開源! 開源邊緣計算正在經(jīng)歷其業(yè)界最具活力的發(fā)展階...
閱讀 1402·2021-11-22 09:34
閱讀 1378·2021-09-22 14:57
閱讀 3400·2021-09-10 10:50
閱讀 1371·2019-08-30 15:54
閱讀 3690·2019-08-29 17:02
閱讀 3472·2019-08-29 12:54
閱讀 2611·2019-08-27 10:57
閱讀 3316·2019-08-26 12:24