Closed thiDucTran closed 2 years ago
I even tried to create the cluster with no CNI (stopping at step https://cluster-api.sigs.k8s.io/user/quick-start.html#deploy-a-cni-solution)
After that I used both helm
and cilium
CLI method to install...same error....the error is mentioned in https://docs.cilium.io/en/stable/gettingstarted/kind/ ....but I am not understanding how my case is related to kind
level=info msg=" --operator-api-serve-addr='127.0.0.1:9234'" subsys=cilium-operator-generic
level=info msg=" --operator-prometheus-serve-addr=':9963'" subsys=cilium-operator-generic
level=info msg=" --parallel-alloc-workers='50'" subsys=cilium-operator-generic
level=info msg=" --pprof='false'" subsys=cilium-operator-generic
level=info msg=" --pprof-port='6061'" subsys=cilium-operator-generic
level=info msg=" --remove-cilium-node-taints='true'" subsys=cilium-operator-generic
level=info msg=" --set-cilium-is-up-condition='true'" subsys=cilium-operator-generic
level=info msg=" --skip-crd-creation='false'" subsys=cilium-operator-generic
level=info msg=" --subnet-ids-filter=''" subsys=cilium-operator-generic
level=info msg=" --subnet-tags-filter=''" subsys=cilium-operator-generic
level=info msg=" --synchronize-k8s-nodes='true'" subsys=cilium-operator-generic
level=info msg=" --synchronize-k8s-services='true'" subsys=cilium-operator-generic
level=info msg=" --unmanaged-pod-watcher-interval='15'" subsys=cilium-operator-generic
level=info msg=" --version='false'" subsys=cilium-operator-generic
level=info msg="Cilium Operator 1.12.2 c7516b9 2022-09-14T15:25:06+02:00 go version go1.18.6 linux/amd64" subsys=cilium-operator-generic
level=info msg="Starting apiserver on address 127.0.0.1:9234" subsys=cilium-operator-api
level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s
level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s
level=error msg="Unable to contact k8s api-server" error="Get \"https://10.96.0.1:443/api/v1/namespaces/kube-system\": dial tcp 10.96.0.1:443: i/o timeout" ipAddr="https://10.96.0.1:443" subsys=k8s
level=fatal msg="Unable to connect to Kubernetes apiserver" error="unable to create k8s client: unable to create k8s client: Get \"https://10.96.0.1:443/api/v1/namespaces/kube-system\": dial tcp 10.96.0.1:443: i/o timeout" subsys=cilium-operator-generic
this seems to be an IP confict on our end when subnetting. sorry all
No apologies necessary, perhaps this info will help someone else when searching through the historical issue queue, thanks for being thorough!
@thiDucTran thanks for keeping us posted! I'm planning on adding some instructions to docs on setting up Cilium and maybe an e2e test too
hi for full clarity I changed the CIDR as below and cilium + hubble was installed fine via CRS (passing connectivity test etc) ...which is why I deduced it to being some IP conflict with another associate of mine that is also playing with CAPI using all defaults (not specifying CIDR blocks etc..)
In conjunction with CRS, I saw that when installing cilium
using cilium CLI it also uses helm
so I copied what cilium
CLI was using to create my manifest files for CRS usage. helm template --namespace kube-system cilium cilium/cilium --version 1.12.2 --set hubble.relay.enabled=true --set hubble.ui.enabled=true --set azure.resourceGroup=om-rd-clusterapi-thi-stage,cluster.id=0,cluster.name=thi-test-cilium,encryption.nodeEncryption=false,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: AzureCluster
metadata:
name: thi-test-cilium
namespace: default
spec:
identityRef:
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: AzureClusterIdentity
name: management-cluster-identity
location: eastus
networkSpec:
vnet:
name: vnet-cilium-stage
cidrBlocks:
- 10.0.0.0/16
subnets:
- name: subnet-control-plane-cilium-stage
role: control-plane
cidrBlocks:
- 10.0.100.0/24
- name: subnet-worker-node-cilium-stage
role: node
cidrBlocks:
- 10.0.101.0/24
I created https://github.com/cilium/cilium/issues/21678 as I think probably the issue is more with Cilium.
But posting here for a 2nd look.
HI, I am trying to create k8s clusters in Azure (not AKS) using these links as guide: https://cluster-api.sigs.k8s.io/user/quick-start.html , https://capz.sigs.k8s.io/topics/getting-started.html , and https://blog.scottlowe.org/2021/10/07/installing-cilium-via-clusterresourceset/
Steps taken:
kind create cluster --name bootstrap-cluster
kubectl cluster-info --context kind-bootstrap-cluster
helm template cilium cilium/cilium --version 1.12.2 --namespace kube-system --set hubble.relay.enabled=true --set hubble.ui.enabled=true >cilium-hubble-1.12.2.yaml
kubectl create configmap cilium-crs-cm --from-file=cilium-hubble-1.12.2.yaml
clusterctl generate cluster thi-test-cilium --kubernetes-version 1.25.2 >cilium.yaml
kubectl apply -f cilium.yaml
my
cilium.yaml
looks like belowhere is
cilium-hubble-1.12.2.yaml
I think there is a networking issue or cilium config related issue? I am just not sure why cilium pods are not restarting in the control plane VM