Calico on RKE cluster on Azure not working

[jympetalmd]

Expected Behavior

Was expecting to just follow the documentation and install Calico. https://projectcalico.docs.tigera.io/getting-started/kubernetes/rancher

Current Behavior

RKE installation can't continue, calico networking isn't working

Possible Solution

Seams to be working fine using this addons: https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/templates/addons/calico.yaml

The ippool are 192.168.x.x but seams to work fine!

Steps to Reproduce (for bugs)

RKE with addons

• https://raw.githubusercontent.com/projectcalico/calico/v3.24.1/manifests/tigera-operator.yaml (CRDs)
• and :

  apiVersion: operator.tigera.io/v1
  kind: Installation
  metadata:
  name: default
  spec:
  calicoNetwork:
  ipPools:
  - blockSize: 26
    cidr: 10.42.0.0/16 #Change based on doc (RKE default CIDR)
    encapsulation: VXLANCrossSubnet
    natOutgoing: Enabled
    nodeSelector: all()
  mtu: 1350 #1450 (default) - trials following lead for Azure
  controlPlaneReplicas: 1
  flexVolumePath: /opt/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds #Flatcar requirements
  ---
  ...
  kind: APIServer 
  ...

Your Environment

RKE Version: 1.3.13 Flatcar Container Linux - 3033.2.3, please see https://rancher.com/docs/rke/latest/en/os/#flatcar-container-linux

[tmjd]

Please provide the specific problem that you are experiencing. I'm not sure what issue you are seeing just based on.

RKE installation can't continue, calico networking isn't working

For example has calico-node deployed, are there errors reported in the kubectl get tigerastatus -o yaml resources, or has operator not even deployed?