首先部署一個k8s 的環境
創建java項目並push到阿里雲
開始部署啓動項目
在master節點上執行
# 查看該容器裏面的鏡像
docker images
# 展示
REPOSITORY TAG IMAGE ID CREATED SIZE
eipwork/kuboard latest 0146965e6475 2 days ago 133MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy v1.16.2 8454cbe08dc9 4 weeks ago 86.1MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager v1.16.2 6e4bffa46d70 4 weeks ago 163MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver v1.16.2 c2c9a0406787 4 weeks ago 217MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler v1.16.2 ebac1ae204a2 4 weeks ago 87.3MB
calico/node v3.9.2 14a380c92c40 4 weeks ago 195MB
calico/cni v3.9.2 c0d73dd53e71 4 weeks ago 160MB
calico/kube-controllers v3.9.2 7f7ed50db9fb 4 weeks ago 56MB
calico/pod2daemon-flexvol v3.9.2 523f0356e07b 6 weeks ago 9.78MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-apiserver v1.16.0 b305571ca60a 7 weeks ago 217MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy v1.16.0 c21b0c7400f9 7 weeks ago 86.1MB
registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager v1.16.0 06a629a7e51c 7 weeks ago 163MB
registry.cn-hangzhou.aliyuncs.com/google_containers/etcd 3.3.15-0 b2756210eeab 2 months ago 247MB
registry.cn-hangzhou.aliyuncs.com/google_containers/coredns 1.6.2 bf261d157914 3 months ago 44.1MB
registry.cn-hangzhou.aliyuncs.com/google_containers/pause 3.1 da86e6ba6ca1 23 months ago 742kB
# 登陸阿里雲
docker login --username=your user name registry.cn-hangzhou.aliyuncs.com
Password: your password
# pull 阿里雲鏡像
docker pull registry.cn-hangzhou.aliyuncs.com/sdongp-dkz/kubernetes:latest
再次查看master 當中的鏡像這個時候就有自己想要的鏡像了
查看 master 已經下載好的鏡像
docker images
# 展示如下
REPOSITORY TAG IMAGE ID CREATED SIZE
registry.cn-hangzhou.aliyuncs.com/sdongp-dkz/kubernetes latest ca3dbc9962c8 49 years ago 119MB
運行鏡像
kubectl run springboot01 --image=registry.cn-hangzhou.aliyuncs.com/sdongp-dkz/kubernetes:latest --port=9000
代碼解釋
springboot01 // 給將要運行的鏡像取名字 可隨意
registry.cn-hangzhou.aliyuncs.com/sdongp-dkz/kubernetes:latest //將要運行的鏡像
9000 //綁定的端口
查看啓動情況
kubectl get pod
NAME READY STATUS RESTARTS AGE
springboot-79b696b8ff-bl7rr 1/1 Running 0 37m
這個時候 STATUS 是 Running
查看更詳細信息
kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
springboot-79b696b8ff-bl7rr 1/1 Running 0 39m 10.100.3.2 k8s-node2 <none> <none>
訪問部署的服務
# 訪問 springboot 服務
curl 10.100.3.2:9000 // 返回hello world (這裏的10.100.3.2是node1的內部ip)
發佈時發現的問題
- 我將鏡像是pull在master 節點的 , 但是我啓動之後發現 node1 節點也有了這個鏡像 並且被啓動了訪問也是正常的 (這裏還需要繼續去研究)
- 我在node2 又pull 了一個同樣的鏡像 也啓動了使用了 springboot01 這個命名也能啓動這個時候不會同步到node1