F5 Solutions for Containers > Appendix Source | Edit on

Appendix 8: Replace Flannel w/ Calico¶

This appendix will walk through the steps to replace Flannel with Calico.

Expected time to complete: 15 minutes

Via RDP connect to the UDF lab “jumpbox” host.

Note

Username and password are: ubuntu/ubuntu

On the jumphost open a terminal and start an SSH session with kube-master1.

# If directed to, accept the authenticity of the host by typing "yes" and hitting Enter to continue.

ssh kube-master1

Remove Flannel¶

Show running Flannel pods
```
kubectl get pods -n kube-system
```

Remove Flannel

kubectl delete -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml

Validate Flannel pods are removed. (Run previous kubectl command)
```
kubectl get pods -n kube-system
```
Note

Run this command several times until you no longer see the “kube-flannel” pods.
Cleanup CIS deployment file.

Note

This step can be skipped but several errors will appear in the CIS pod log.
```
vim ~/agilitydocs/docs/class1/kubernetes/cluster-deployment.yaml
```
Remove “–flannel-name=k8s-tunnel” from the bottom of the file. Be sure to remove the “,” on the line above the removed the line. After editing the file should look like the following:

Install Calico¶

Change local directory to the lab calico dir.
```
cd ~/agilitydocs/docs/class1/kubernetes/calico
```

Download calico manifest

curl https://docs.projectcalico.org/manifests/calico.yaml -O

Modify the manifest with proper POD CIDR

Important

This lab was built with Flannel and the default POD CIDR of 10.244.0.0/16. The calico.yaml manifest uses 192.168.0.0/16 so has to be adjusted.
```
vim calico.yaml
```
Note

If unfamiliar with VI the instructor will walk you through the commands.

Find the “CALICO__IPV4POOL_CIDR variable and uncomment the two lines as shown below. Replacing “192.168.0.0/16” with “10.244.0.0/16”
Start Calico on the cluster
```
kubectl apply -f calico.yaml
```
Validate Calico pods are installed and running
```
kubectl get pods -n kube-system
```

Install calicoctl¶

Retrieve the calicoctl binary

curl -O -L https://github.com/projectcalico/calicoctl/releases/download/v3.15.1/calicoctl

chmod +x calicoctl

sudo mv calicoctl /usr/local/bin

Copy the the calicoctl.cfg file to /etc/calico/

apiVersion: projectcalico.org/v3
kind: CalicoAPIConfig
metadata:
spec:
  datastoreType: "kubernetes"
  kubeconfig: "/home/ubuntu/.kube/config"

sudo mkdir /etc/calico

sudo cp calicoctl.cfg /etc/calico/

Verify calicoctl is properly set up
```
calicoctl get nodes
```

Set up the Calico BGP config

apiVersion: projectcalico.org/v3
kind: BGPConfiguration
metadata:
  name: default
spec:
  logSeverityScreen: Info
  nodeToNodeMeshEnabled: true
  asNumber: 64512

calicoctl create -f caliconf.yaml

Set up the BIG-IP BGP peer

apiVersion: projectcalico.org/v3
kind: BGPPeer
metadata:
  name: bgppeer-global-bigip1
spec:
  peerIP: 10.1.1.4
  asNumber: 64512

calicoctl create -f calipeer.yaml

Verify setup
```
calicoctl get bgpPeer
```
Change dir back to working lab directory

Note

The necessary kubernetes lab files can be found in this directory.
```
cd ..

# or

cd ~/agilitydocs/docs/class1/kubernetes/
```

Confgure BIG-IP for Calico¶

Open firefox and connect to bigip1 management console. For your convenience there’s a shortcut on the firefox toolbar.

Note

Username and password are: admin/admin

Enable BGP on route domain 0
1. Connect to the BIG-IP GUI and go to Network ‣ Route Domains
2. Click on “0” to open route domain 0
3. Under Dynamic Routing Protocols, move “BGP” from Available to Enabled
4. Click Update

Open a new terminal tab and SSH to BIG-IP

# If directed to, accept the authenticity of the host by typing "yes" and hitting Enter to continue.

# passwd = admin

ssh admin@10.1.1.4

Configure BGP

#access the IMI Shell
imish

#Switch to enable mode
enable

#Enter configuration mode
config terminal
#Setup route bgp with AS Number 64512
router bgp 64512

#Create BGP Peer group
neighbor calico-k8s peer-group

#assign peer group as BGP neighbors
neighbor calico-k8s remote-as 64512

#we need to add all the peers: the other BIG-IP, our k8s components
neighbor 10.1.1.7 peer-group calico-k8s
neighbor 10.1.1.8 peer-group calico-k8s
neighbor 10.1.1.9 peer-group calico-k8s

#on BIG-IP 1, run
neighbor 10.1.1.24 peer-group calico-k8s

#on BIG-IP 2, run
neighbor  10.1.1.4 peer-group calico-k8s

#save configuration
write

#exit
end

Verify BGP is running
```
show ip bgp neighbors
```
Check BIG-IP routes
```
exit # Exit Zebos first

route
```

Previous Next