Skip to main content
Stack Overflow
  1. About
  2. For Teams

Return to Revisions

2 of 3
added 241 characters in body; edited title
marc_s
  • 760.3k
  • 186
  • 1.4k
  • 1.5k

Cilium installation

I'm trying to install Cilium in Windows 10 with these configuration:

  • minikube version: v1.26.0
  • Kubectl version:
Client Version: version.Info { Major: "1", Minor: "24", 
 GitVersion: "v1.24.1", 
 GitCommit:"3ddd0f45aa91e2f30c70734b175631bec5b5825a", 
 GitTreeState: "clean", 
 BuildDate: "2022幓05月24ę—„T12:26:19Z", 
 GoVersion: "go1.18.2", 
 Compiler: "gc", 
 Platform: "windows/amd64" }
Kustomize Version: v4.5.4
  • Cilium version:
cilium-cli: v0.11.11 compiled with go1.18.3 on windows/amd64
cilium image (default): v1.11.6

When I do

minikube start --network-plugin=cni --cni=false

And then download the latest Cilium version:

Cilium -> download cilium-windows-amd64.tar.gz
Release v0.11.11 Latest

And then install Cilium:

cilium install

this error appears

šŸ”® Auto-detected Kubernetes kind: minikube
✨ Running "minikube" validation checks
āœ… Detected minikube version "1.26.0"
iļø Using Cilium version 1.11.6
šŸ”® Auto-detected cluster name: minikube
šŸ”® Auto-detected datapath mode: tunnel
iļø helm template --namespace kube-system cilium cilium/cilium --version 1.11.6 --set cluster.id=0,cluster.name=minikube,encryption.nodeEncryption=false,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan
iļø Storing helm values file in kube-system/cilium-cli-helm-values Secret
šŸ”‘ Created CA in secret cilium-ca
šŸ”‘ Generating certificates for Hubble...
šŸš€ Creating Service accounts...
šŸš€ Creating Cluster roles...
šŸš€ Creating ConfigMap for Cilium version 1.11.6...
šŸš€ Creating Agent DaemonSet...
level=warning msg="spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[1].matchExpressions[0].key: beta.kubernetes.io/os is deprecated since v1.14; use \"kubernetes.io/os\" instead" subsys=klog
šŸš€ Creating Operator Deployment...
āŒ› Waiting for Cilium to be installed and ready...
 / Ģ„ Ģ„\
 / Ģ„ Ģ„\__/ Ģ„ Ģ„\ Cilium: 2 errors
 \__/ Ģ„ Ģ„\__/ Operator: OK
 / Ģ„ Ģ„\__/ Ģ„ Ģ„\ Hubble: disabled
 \__/ Ģ„ Ģ„\__/ ClusterMesh: disabled
 \__/
DaemonSet cilium Desired: 1, Unavailable: 1/1
Deployment cilium-operator Desired: 1, Ready: 1/1, Available: 1/1
Containers: cilium Running: 1
Cluster Pods: 0/0 managed by Cilium
Image versions cilium quay.io/cilium/cilium:v1.11.6@sha256:f7f93c26739b6641a3fa3d76b1e1605b15989f25d06625260099e01c8243f54c: 1
Errors: cilium cilium 1 pods of DaemonSet cilium are not ready
 cilium cilium-d2jp4 unable to retrieve cilium status: unable to upgrade connection: container not found ("cilium-agent")
ā†©ļø Rolling back installation...
Error: Unable to install Cilium: timeout while waiting for status to become successful: context deadline exceeded

What can be happen

Daniel
  • 69
  • 1
  • 3
  • 11
lang-yaml

AltStyle ć«ć‚ˆć£ć¦å¤‰ę›ć•ć‚ŒćŸćƒšćƒ¼ć‚ø (->ć‚ŖćƒŖć‚øćƒŠćƒ«) /