Professional Documents
Culture Documents
Calico Installation Process
Calico Installation Process
2. $ curl
https://raw.githubusercontent.com/projectcalico/calico/v3.24.5/manifests/
calico.yaml -O
3. If you are using pod CIDR 192.168.0.0/16, skip to the next step. If you are
using a different pod CIDR with kubeadm, no changes are required - Calico
will automatically detect the CIDR based on the running configuration. For
other platforms, make sure you uncomment the CALICO_IPV4POOL_CIDR
variable in the manifest and set it to the same value as your chosen pod
CIDR.
4. Customize the manifest as necessary.
5. Apply the manifest using the following command.
2. $ curl
https://raw.githubusercontent.com/projectcalico/calico/v3.24.5/manifests/
calico-typha.yaml -o calico.yaml
3. If you are using pod CIDR 192.168.0.0/16, skip to the next step. If you are
using a different pod CIDR with kubeadm, no changes are required - Calico
will automatically detect the CIDR based on the running configuration. For
other platforms, make sure you uncomment the CALICO_IPV4POOL_CIDR
variable in the manifest and set it to the same value as your chosen pod
CIDR.
4. Modify the replica count to the desired number in
the Deployment named, calico-typha.
5. apiVersion: apps/v1beta1
6. kind: Deployment
7. metadata:
8. name: calico-typha
9. ...
10. spec:
11. ...
We recommend at least one replica for every 200 nodes, and no more than
20 replicas. In production, we recommend a minimum of three replicas to
reduce the impact of rolling upgrades and failures. The number of replicas
should always be less than the number of nodes, otherwise rolling upgrades
will stall. In addition, Typha only helps with scale if there are fewer Typha
instances than there are nodes.
Warning: If you set typha_service_name and set the Typha deployment
replica count to 0, Felix will not start.