docker calico安装
2024-10-21 06:43:08
第一步，安装etcd:
请参考以前的文章: http://www.cnblogs.com/vincenshen/articles/8637949.html
第二步，下载calico:
sudo wget -O /usr/local/bin/calicoctl https://github.com/projectcalico/calicoctl/releases/download/v1.6.3/calicoctl
sudo chmod +x /usr/local/bin/calicoctl
第三步，编写calico配置文件:
apiVersion: v1
kind: calicoApiConfig
metadata:
spec:
datastoreType: "etcdv2"
etcdEndpoints: "http://etcd:2379"
第四步，运行calico node:
root@Docker003:~# sudo calicoctl node run --node-image=quay.io/calico/node:v2.6.8
sudo: unable to resolve host Docker003
Running command to load modules: modprobe -a xt_set ip6_tables
Enabling IPv4 forwarding
Enabling IPv6 forwarding
Increasing conntrack limit
Removing old calico-node container (if running).
Running the following command to start calico-node: docker run --net=host --privileged --name=calico-node -d --restart=always -e NODENAME=Docker003 -e CALICO_NETWORKING_BACKEND=bird -e CALICO_LIBNETWORK_ENABLED=true -e ETCD_ENDPOINTS=http://172.16.65.151:2379 -v /var/log/calico:/var/log/calico -v /var/run/calico:/var/run/calico -v /lib/modules:/lib/modules -v /run:/run -v /run/docker/plugins:/run/docker/plugins -v /var/run/docker.sock:/var/run/docker.sock quay.io/calico/node:v2.6.8 Image may take a short time to download if it is not available locally.
Container started, checking progress logs. -- ::40.421 [INFO][] startup.go : Early log level set to info
-- ::40.422 [INFO][] client.go : Loading config from environment
-- ::40.422 [INFO][] startup.go : Skipping datastore connection test
-- ::40.424 [INFO][] startup.go : Building new node resource Name="Docker003"
-- ::40.424 [INFO][] startup.go : Initialise BGP data
-- ::40.425 [INFO][] startup.go : Using autodetected IPv4 address on interface ens33: 172.16.65.153/
-- ::40.425 [INFO][] startup.go : Node IPv4 changed, will check for conflicts
-- ::40.431 [INFO][] startup.go : No AS number configured on node resource, using global value
-- ::40.434 [INFO][] etcd.go : Ready flag is already set
-- ::40.435 [INFO][] client.go : Using previously configured cluster GUID
-- ::40.450 [INFO][] compat.go : Returning configured node to node mesh
-- ::40.460 [INFO][] startup.go : Using node name: Docker003
-- ::40.529 [INFO][] client.go : Loading config from environment
Starting libnetwork service
Calico node started successfully
calico node会以container方式运行
第五步，查看运行结果：
root@Docker003:~# calicoctl node status
Calico process is running. IPv4 BGP status
+---------------+-------------------+-------+----------+-------------+
| PEER ADDRESS | PEER TYPE | STATE | SINCE | INFO |
+---------------+-------------------+-------+----------+-------------+
| 172.16.65.152 | node-to-node mesh | up | :: | Established |
+---------------+-------------------+-------+----------+-------------+ IPv6 BGP status
No IPv6 peers found.
第六步，创建calico网络
创建的calico网络会自动同步到其他Docker主机上
root@Docker003:~# docker network create --driver calico --ipam-driver calico-ipam calico_network01
0765e8cf3d7867715783f607d5fc1d8b54ef972ff697960c63aaf532d2900c51
root@Docker003:~# docker network ls
NETWORK ID NAME DRIVER SCOPE
d3436c79a405 bridge bridge local
0765e8cf3d78 calico_network01 calico global
5de037f95399 host host local
f4305d9ce150 none null local
第七步，运行container
root@Docker003:~# docker run -itd --network calico_network01 --name bbox1 busybox
// calico并没有在Docker主机上创建bridge
root@Docker003:~# brctl show
bridge name bridge id STP enabled interfaces
docker0 .0242c840a49d no // 多了一个calico veth pair
root@Docker003:~# ip a
: lo: <LOOPBACK,UP,LOWER_UP> mtu qdisc noqueue state UNKNOWN group default qlen
link/loopback ::::: brd :::::
inet 127.0.0.1/ scope host lo
valid_lft forever preferred_lft forever
inet6 ::/ scope host
valid_lft forever preferred_lft forever
: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu qdisc pfifo_fast state UP group default qlen
link/ether :0c::0f::b7 brd ff:ff:ff:ff:ff:ff
inet 172.16.65.153/ brd 172.16.65.255 scope global ens33
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:fe0f:79b7/ scope link
valid_lft forever preferred_lft forever
: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu qdisc noqueue state DOWN group default
link/ether ::c8::a4:9d brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/ brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
: calia9212856e7c@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu qdisc noqueue state UP group default
link/ether :3c:::7e: brd ff:ff:ff:ff:ff:ff link-netnsid
inet6 fe80::903c:80ff:fe31:7e18/ scope link
valid_lft forever preferred_lft forever
// container的网络和Docker主机通过calico veth pair连接
root@Docker003:~# docker exec bbox1 ip a
: lo: <LOOPBACK,UP,LOWER_UP> mtu qdisc noqueue qlen
link/loopback ::::: brd :::::
inet 127.0.0.1/ scope host lo
valid_lft forever preferred_lft forever
: cali0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu qdisc noqueue
link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.109.128/ brd 192.168.109.128 scope global cali0
valid_lft forever preferred_lft forever
在其他Docker主机上也运行Container并加入相同的Calico网络
root@Docker003:~# ip route
default via 172.16.65.2 dev ens33 onlink
172.16.65.0/ dev ens33 proto kernel scope link src 172.16.65.153
172.17.0.0/ dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.109.128 dev calia9212856e7c scope link
blackhole 192.168.109.128/ proto bird
192.168.214.64/ via 172.16.65.152 dev ens33 proto bird
在多个Docker主机上运行Container连接到同一个calico网络测试连通性
root@Docker002:~# docker exec bbox2 ping -c bbox1
PING bbox1 (192.168.109.128): data bytes
bytes from 192.168.109.128: seq= ttl= time=0.447 ms
bytes from 192.168.109.128: seq= ttl= time=1.328 ms --- bbox1 ping statistics ---
packets transmitted, packets received, % packet loss
round-trip min/avg/max = 0.447/0.887/1.328 ms
calico为Container提供DNS服务。
第八步，为calico配置Policy
calico 默认的 policy 规则是：容器只能与同一个 calico 网络中的容器通信。
root@Docker002:~# calicoctl get profile calico_network01 -o yaml
- apiVersion: v1
kind: profile
metadata:
name: calico_network01
tags:
- calico_network01
spec:
egress:
- action: allow
destination: {}
source: {}
ingress:
- action: allow
destination: {}
source:
tag: calico_network01
编写policy yml文件
root@Docker003:~# vim test_ping.yml - apiVersion: v1
kind: profile
metadata:
name: calico_network02
spec:
ingress:
- action: allow
protocol: icmp
source:
tag: calico_network01
destination: {}
应用policy
root@Docker003:~# calicoctl apply -f test_ping.yml
Successfully applied 'profile' resource(s)
最新文章
- 微软Azure 经典模式下创建内部负载均衡（ILB）
- 数据库.bak文件还原报错的处理办法
- Mac 连接阿里云服务器
- Shell脚本_位置参数和预定义参数
- 【bzoj2190】 SDOI2008—仪仗队
- CentOS 6.4下编译安装 gcc-4.8.0（转）
- 31. Flatten Binary Tree to Linked List
- angularjs入门学习【应用剖析中篇】
- GoJS研究，简单图表制作。
- 【leetcode列】3Sum
- Android 儿子Activity在启动过程中的流程组件 &amp;&amp; 儿子Activity在一个新的进程组件启动过程
- 《C++ Primer》之重载操作符与转换（中）
- js 弹层 提示
- libpng+VS2012(VS2015)的使用
- CDH集成Kafka,两种方式：离线、在线
- winform 打印时的默认单位
- js生成带有logo的二维码并保存成图片下载
- D. Equalize Them All Codeforces Round #550 (Div. 3)
- 【python014--字符串内置函数】
- Java语法基础学习DayEight