docker 如何加入kubernetes_Kubernetes 实战教学,手把手教您用2个脚本在 PWK上启用 Compose...

51e0be862c1b48f95b3301e194fb6522.png

每周一、三、五,与您不见不散!


在 Dockercon 的第二天,Docker 在 Kubernetes 项目上开源了 Compose。这个工具无疑可以简化 Kubernetes。如果您不知道,Docker 企业版已经在 Compose File 3.3 版本中启用了这个功能,它可以让您使用相同的 docker-compose.yml 文件进行 Swarm 部署,也可以在部署应用栈时指定 Kubernetes 工作负载。


8ddcb2666102482381b08d66a6cd62cc.png

两周前,我注意到社区中有人要求在 Kubernetes Playground 上运行 Compose on Kubernetes。出于我的兴趣,我开始研究如何简化解决方案,以便任何人都能在短时间内轻松地设置它。我创建了镜像仓库,并开始构建一个简单的脚本和 Makefile 来启动它并在 PWK 上运行。点击下列文章标题,查看详情:

  • Kubernetes实战教学,手把手教您如何在K8s平台上使用 Compose 1;
  • Kubernetes实战教学,手把手教您如何在K8s平台上使用 Compose 2;

在这篇博文中,我将向您演示如何使用2个脚本就可以在 Play with Kubernetes 平台上启用 Compose on Kubernetes。接下来,让我们开始吧!


首先,浏览 https://labs.play-with-k8s.com/ 访问Kubernetes Playground。

2eedc3b2e4cbee0d838051c8a8ddb053.png

单击“Login”按钮,并使用 Docker Hub 或 GitHub ID 进行身份验证。

65470bd733c4d91257a06f5962e15d77.png

一旦开始会话,您将拥有一个自己的实验室环境。


添加第一个 Kubernetes 节点

单击左侧的“Add New Instance” 来建您的第一个 Kubernetes 集群节点。它会自动将其命名为“node1”。每个实例都预装了Docker Community Edition(CE)和Kubeadm。该节点将被视为我们群集的主节点。

8845ab9137e9151b69c98a81424045b7.png

引导主节点

克隆镜像仓库并在第一个实例上运行此脚本

git clone https://github.com/collabnix/compose-on-kubernetescd compose-on-kubernetes/scripts/pwk/sh bootstrap-pwk.sh

当您执行此脚本时,作为初始化的一部分,kubeadm 会编写所需的几个配置文件,设置 RBAC 并部署 Kubernetes 控制平面组件(如 kube-apiserver、kube-dns、kube-proxy 和 etcd 等)。控制平面组件部署为 Docker 容器。

75d7c6c58ed79e4fabe4dc82ac14a795.png

复制上面的 kubeadm 连接令牌命令并将其保存,以供下一步使用。此命令将用于将其他节点加入群集。


添加工作节点

751deeab83856aa9953392178c74db03.png

点击“Add New Node”来添加一个新的工作节点。


检查集群状态

[node1 ~]$ kubectl get nodesNAME STATUS ROLES AGE VERSIONnode1 Ready master 18m v1.11.3node2 Ready 4m v1.11.3node3 Ready 39s v1.11.3node4 NotReady 22s v1.11.3node5 NotReady 4s v1.11.3
[node1 ]$ kubectl get poNo resources found.
[node1 ]$ kubectl get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEkubernetes ClusterIP 10.96.0.1 443/TCP 1h

执行以下脚本,一次性设置好 Compose Namespace、etcd cluster 和 Compose controller:

chmod +x prepare-pwk.shsh prepare-pwk.sh[node1 pwk]$ sh prepare-pwk.shCreating Compose Namespace...namespace/compose createdInstalling Helm... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed100 21.6M 100 21.6M 0 0 25.3M 0 --:--:-- --:--:-- --:--:-- 25.4MPreparing Helmlinux-amd64/linux-amd64/tillerlinux-amd64/helmlinux-amd64/LICENSElinux-amd64/README.mdCreating tiller under kube-system namespace...serviceaccount/tiller createdclusterrolebinding.rbac.authorization.k8s.io/tiller-cluster-rule createdCreating /root/.helmCreating /root/.helm/repositoryCreating /root/.helm/repository/cacheCreating /root/.helm/repository/localCreating /root/.helm/pluginsCreating /root/.helm/startersCreating /root/.helm/cache/archiveCreating /root/.helm/repository/repositories.yamlAdding stable repo with URL: https://kubernetes-charts.storage.googleapis.comAdding local repo with URL: http://127.0.0.1:8879/charts$HELM_HOME has been configured at /root/.helm. Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster. Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.To prevent this, run `helm init` with the --tiller-tls-verify flag.For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installationHappy Helming! Tiller is still coming up...Please WaitNAME READY STATUS RESTARTS AGEcoredns-78fcdf6894-699fx 1/1 Running 0 5mcoredns-78fcdf6894-trslx 1/1 Running 0 5metcd-node1 1/1 Running 0 4mkube-apiserver-node1 1/1 Running 0 4mkube-controller-manager-node1 1/1 Running 0 4mkube-proxy-5gskp 1/1 Running 0 4mkube-proxy-5hbkb 1/1 Running 0 5mkube-proxy-lcsnz 1/1 Running 0 4mkube-scheduler-node1 1/1 Running 0 4mtiller-deploy-85744d9bfb-bjw2f 0/1 Running 0 15sweave-net-9vt2s 2/2 Running 1 4mweave-net-k87d7 2/2 Running 0 5mweave-net-nmmt5 2/2 Running 0 4mNAME: etcd-operatorLAST DEPLOYED: Mon Jan 21 14:27:50 2019NAMESPACE: composeSTATUS: DEPLOYED RESOURCES:==> v1/ServiceAccountNAME SECRETS AGEetcd-operator-etcd-operator-etcd-backup-operator 1 4setcd-operator-etcd-operator-etcd-operator 1 4setcd-operator-etcd-operator-etcd-restore-operator 1 4s ==> v1beta1/ClusterRoleNAME AGEetcd-operator-etcd-operator-etcd-operator 4s ==> v1beta1/ClusterRoleBindingNAME AGEetcd-operator-etcd-operator-etcd-backup-operator 4setcd-operator-etcd-operator-etcd-operator 3setcd-operator-etcd-operator-etcd-restore-operator 3s ==> v1/ServiceNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEetcd-restore-operator ClusterIP 10.108.89.92 19999/TCP 3s ==> v1beta2/DeploymentNAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGEetcd-operator-etcd-operator-etcd-backup-operator 1 1 1 0 3setcd-operator-etcd-operator-etcd-operator 1 1 1 0 3setcd-operator-etcd-operator-etcd-restore-operator 1 1 1 0 3s ==> v1/Pod(related)NAME READY STATUS RESTARTS AGEetcd-operator-etcd-operator-etcd-backup-operator-56fd448cd897mk 0/1 ContainerCreating 0 2setcd-operator-etcd-operator-etcd-operator-c5b8b8f74-pttr2 0/1 ContainerCreating 0 2setcd-operator-etcd-operator-etcd-restore-operator-58587cdc9g4br 0/1 ContainerCreating 0 2s  NOTES:1. etcd-operator deployed. If you would like to deploy an etcd-cluster set cluster.enabled to true in values.yaml Check the etcd-operator logs export POD=$(kubectl get pods -l app=etcd-operator-etcd-operator-etcd-operator --namespacecompose --output name) kubectl logs $POD --namespace=composeLoaded plugins: fastestmirror, ovlbase | 3.6 kB 00:00:00docker-ce-stable | 3.5 kB 00:00:00extras | 3.4 kB 00:00:00kubernetes/signature | 454 B 00:00:00kubernetes/signature | 1.4 kB 00:00:10 !!!updates | 3.4 kB 00:00:00(1/7): base/7/x86_64/group_gz | 166 kB 00:00:00(2/7): extras/7/x86_64/primary_db | 156 kB 00:00:00(3/7): base/7/x86_64/primary_db | 6.0 MB 00:00:00(4/7): updates/7/x86_64/primary_db | 1.3 MB 00:00:00(5/7): docker-ce-stable/x86_64/primary_db | 20 kB 00:00:00(6/7): docker-ce-stable/x86_64/updateinfo | 55 B 00:00:01(7/7): kubernetes/primary | 42 kB 00:00:01Determining fastest mirrors * base: mirror.nl.datapacket.com * extras: mirror.nl.datapacket.com * updates: mirror.denit.netkubernetes 305/305Resolving Dependencies--> Running transaction check---> Package wget.x86_64 0:1.14-18.el7 will be installed--> Finished Dependency Resolution Dependencies Resolved =============================================================================================== Package Arch Version Repository Size===============================================================================================Installing: wget x86_64 1.14-18.el7 base 547 k Transaction Summary===============================================================================================Install 1 Package Total download size: 547 kInstalled size: 2.0 MDownloading packages:wget-1.14-18.el7.x86_64.rpm | 547 kB 00:00:00Running transaction checkRunning transaction testTransaction test succeededRunning transaction Installing : wget-1.14-18.el7.x86_64 1/1install-info: No such file or directory for /usr/share/info/wget.info.gz Verifying : wget-1.14-18.el7.x86_64 1/1 Installed: wget.x86_64 0:1.14-18.el7 Complete!$HELM_HOME has been configured at /root/.helm. Tiller (the Helm server-side component) has been upgraded to the current version.Happy Helming!etcdcluster.etcd.database.coreos.com/compose-etcd createdNAME READY STATUS RESTARTS AGEcoredns-78fcdf6894-699fx 1/1 Running 0 6mcoredns-78fcdf6894-trslx 1/1 Running 0 6metcd-node1 1/1 Running 0 5mkube-apiserver-node1 1/1 Running 0 6mkube-controller-manager-node1 1/1 Running 0 5mkube-proxy-5gskp 1/1 Running 0 6mkube-proxy-5hbkb 1/1 Running 0 6mkube-proxy-lcsnz 1/1 Running 0 5mkube-scheduler-node1 1/1 Running 0 5mtiller-deploy-85744d9bfb-bjw2f 1/1 Running 0 1mweave-net-9vt2s 2/2 Running 1 6mweave-net-k87d7 2/2 Running 0 6mweave-net-nmmt5 2/2 Running 0 5m--2019-01-21 14:28:49-- https://github.com/docker/compose-on-kubernetes/releases/download/v0.4.18/installer-linuxResolving github.com (github.com)... 140.82.118.3, 140.82.118.4Connecting to github.com (github.com)|140.82.118.3|:443... connected.HTTP request sent, awaiting response... 302 FoundLocation: https://github-production-release-asset-2e65be.s3.amazonaws.com/158560458/e9a86500-15b2-11e9-8620-1eec5bf160e3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190121%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190121T142850Z&X-Amz-Expires=300&X-Amz-Signature=bd4020beb0f68210e2a3cfa8ca8166dddcf1d1e4868737eb9ad83363cd39c660&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dinstaller-linux&response-content-type=application%2Foctet-stream [following]--2019-01-21 14:28:50-- https://github-production-release-asset-2e65be.s3.amazonaws.com/158560458/e9a86500-15b2-11e9-8620-1eec5bf160e3?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190121%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190121T142850Z&X-Amz-Expires=300&X-Amz-Signature=bd4020beb0f68210e2a3cfa8ca8166dddcf1d1e4868737eb9ad83363cd39c660&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dinstaller-linux&response-content-type=application%2Foctet-streamResolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... 52.216.161.163Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|52.216.161.163|:443... connected.HTTP request sent, awaiting response... 200 OKLength: 28376064 (27M) [application/octet-stream]Saving to: 'installer-linux' 100%[=====================================================>] 28,376,064 15.9MB/s in 1.7s 2019-01-21 14:28:52 (15.9 MB/s) - 'installer-linux' saved [28376064/28376064] INFO[0000] Checking installation stateINFO[0000] Install image with tag "v0.4.18" in namespace "compose"INFO[0000] Api server: image: "docker/kube-compose-api-server:v0.4.18
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值