Skip to main content
Version: latest

Calico

warning

Limitations: AWS, VMWare supports IP-in-IP encapsulation type. Azure supports VXLAN encapsulation type.

Versions Supported​

Create Bind Mounts for Edge Deployments​

In Edge deployments, Calico requires a bind mount on the host machine. Without the bind mount, it's possible for the Calico pods to be stuck in the init state. Use the following example to create a bind mount from /var/lib/calico on the Edge host. When you build an installer ISO with the bind_mounts block, the folders specified in the block will be mounted. For more information about building the installer ISO, refer to Build Installer ISO.

#cloud-config
stylus:
  site:
    debug: true
    insecureSkipVerify: false
    paletteEndpoint: api.console.spectrocloud.com
    name: edge-appliance-1
    caCerts:
      - |
        -----BEGIN CERTIFICATE-----

        -----END CERTIFICATE-----

install:
  bind_mounts:
    - /var/lib/calico

Troubleshooting​

The following are some tips to troubleshoot issues with the Calico CNI.

  • A daemon set is installed, the calico-node pod should be deployed on all the nodes in the cluster to provide networking.

  • For any issues with networking, check the logs of the calico-node and calico-kube-controller pods on the cluster.

Terraform​

Use the following Terraform snippet to reference the Calico CNI pack in your Terraform template.


data "spectrocloud_registry" "public_registry" {
  name = "Public Repo"
}

data "spectrocloud_pack_simple" "calico" {
  name    = "cni-calico"
  version = "3.27.0"
  type = "helm"
  registry_uid = data.spectrocloud_registry.public_registry.id
}

References​