{"id":18913,"date":"2022-09-23T17:44:53","date_gmt":"2022-09-23T15:44:53","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=18913"},"modified":"2022-09-23T17:44:54","modified_gmt":"2022-09-23T15:44:54","slug":"cilium-installation-in-minikube-using-a-multi-cluster-environment","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/","title":{"rendered":"Cilium installation in Minikube using a multi-cluster environment"},"content":{"rendered":"\n<p>In this post I&#8217;ll share my experience with installing Cilium in Minikube on my Mac. It was not that hard but I faced an issue I had to troubleshoot. I&#8217;ll also show you how to create several Kubernetes clusters in Minikube in order to have one with Calico as CNI and another one with Cilium as CNI. This way I can switch from one to the other according to my needs.<\/p>\n\n\n\n<p>Cilium is a Container Network Interface (CNI) based on eBPF (a recent linux kernel technology that offers better performance than the traditional iptables) which provides network connectivity between the pods as does Calico, Flannel, Weave,&#8230; In addition to CNI, Cilium provides also more advanced features in Networking, Observability and Security.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Calico Cluster in Minikube<\/h2>\n\n\n\n<p>Let&#8217;s start by creating our Calico cluster in Minikube with the following command:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % minikube start --nodes 2 --network-plugin=cni --cni=calico -p cluster-calico\n<\/pre><\/div>\n\n\n<p>With this command I&#8217;ll start a cluster with 2 nodes and use Calico as CNI. The name of this cluster is <strong><em>cluster-calico<\/em><\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cilium Cluster in Minikube<\/h2>\n\n\n\n<p>The installation instructions are provided on the Cilium website and include instructions for a cluster using Minikube: <a href=\"https:\/\/docs.cilium.io\/en\/stable\/gettingstarted\/k8s-install-default\/\">https:\/\/docs.cilium.io\/en\/stable\/gettingstarted\/k8s-install-default\/<\/a><\/p>\n\n\n\n<p>By adapting those instructions we can now create another cluster in Minikube as follows:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % minikube start --nodes 3 --network-plugin=cni --cni=false -p cluster-cilium\n<\/pre><\/div>\n\n\n<p>This cluster is named <strong><em>cluster-cilium<\/em><\/strong> and will have 3 nodes and will be ready to use the cilium.<\/p>\n\n\n\n<p>Then we can install Cilium CLI and Cilium as per the instructions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The issue<\/h2>\n\n\n\n<p>Unfortunately, the Cilium installation didn&#8217;t complete as expected, below is the output of the <strong>cilium install<\/strong> command:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % cilium install\nUsing Cilium version 1.12.1\nAuto-detected cluster name: cluster-cilium\nAuto-detected datapath mode: tunnel\nAuto-detected kube-proxy has been installed\nhelm template --namespace kube-system cilium cilium\/cilium --version 1.12.1 --set cluster.id=0,cluster.name=cluster-cilium,encryption.nodeEncryption=false,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\nStoring helm values file in kube-system\/cilium-cli-helm-values Secret\nCreated CA in secret cilium-ca\nGenerating certificates for Hubble...\nCreating Service accounts...\nCreating Cluster roles...\nCreating ConfigMap for Cilium version 1.12.1...\nCreating Agent DaemonSet...\nCreating Operator Deployment...\nWaiting for Cilium to be installed and ready...\n    \/\u00af\u00af\\\n \/\u00af\u00af\\__\/\u00af\u00af\\    Cilium:         1 errors, 3 warnings\n \\__\/\u00af\u00af\\__\/    Operator:       OK\n \/\u00af\u00af\\__\/\u00af\u00af\\    Hubble:         disabled\n \\__\/\u00af\u00af\\__\/    ClusterMesh:    disabled\n    \\__\/\n\nDeployment        cilium-operator    Desired: 1, Ready: 1\/1, Available: 1\/1\nDaemonSet         cilium             Desired: 3, Unavailable: 3\/3\nContainers:       cilium             Pending: 3\n                  cilium-operator    Running: 1\nCluster Pods:     0\/1 managed by Cilium\nImage versions    cilium             quay.io\/cilium\/cilium:v1.12.1@sha256:ea2db1ee21b88127b5c18a96ad155c25485d0815a667ef77c2b7c7f31cab601b: 3\n                  cilium-operator    quay.io\/cilium\/operator-generic:v1.12.1@sha256:93d5aaeda37d59e6c4325ff05030d7b48fabde6576478e3fdbfb9bb4a68ec4a1: 1\nErrors:           cilium             cilium          3 pods of DaemonSet cilium are not ready\nWarnings:         cilium             cilium-ccmms    pod is pending\n                  cilium             cilium-hlwvq    pod is pending\n                  cilium             cilium-vpjbq    pod is pending\n\u21a9\ufe0f Rolling back installation...\n\nError: Unable to install Cilium: timeout while waiting for status to become successful: context deadline exceeded\n<\/pre><\/div>\n\n\n<p>We can see that the cilium pod stay in the pending state and so the installation fails. This is confirmed with the following command that gives more information:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % k get po -n kube-system\nNAME                                     READY   STATUS                  RESTARTS      AGE\ncilium-operator-6f5c6f768d-zpgjl         1\/1     Running                 0             7m5s\ncilium-pw7bm                             0\/1     Init:ImagePullBackOff   0             7m5s\ncilium-qnf4j                             0\/1     Init:ImagePullBackOff   0             7m5s\ncilium-wzz2t                             0\/1     Init:ImagePullBackOff   0             7m5s\n<\/pre><\/div>\n\n\n<p>The Events section of one of those pod (using <strong>kubectl describe pod cilium-pw7bm -n kube-system<\/strong>) gives the output below:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nEvents:\n  Type     Reason     Age                    From               Message\n  ----     ------     ----                   ----               -------\n  Normal   Scheduled  7m21s                  default-scheduler  Successfully assigned kube-system\/cilium-pw7bm to cluster-cilium-m03\n  Normal   Pulling    2m44s (x3 over 7m20s)  kubelet            Pulling image &quot;quay.io\/cilium\/cilium:v1.12.1@sha256:ea2db1ee21b88127b5c18a96ad155c25485d0815a667ef77c2b7c7f31cab601b&quot;\n  Warning  Failed     45s (x3 over 5m21s)    kubelet            Failed to pull image &quot;quay.io\/cilium\/cilium:v1.12.1@sha256:ea2db1ee21b88127b5c18a96ad155c25485d0815a667ef77c2b7c7f31cab601b&quot;: rpc error: code = Unknown desc = context deadline exceeded\n  Warning  Failed     45s (x3 over 5m21s)    kubelet            Error: ErrImagePull\n  Normal   BackOff    7s (x5 over 5m21s)     kubelet            Back-off pulling image &quot;quay.io\/cilium\/cilium:v1.12.1@sha256:ea2db1ee21b88127b5c18a96ad155c25485d0815a667ef77c2b7c7f31cab601b&quot;\n  Warning  Failed     7s (x5 over 5m21s)     kubelet            Error: ImagePullBackOff\n<\/pre><\/div>\n\n\n<p>The kubelet failed to pull the required image for this pod.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The solution<\/h2>\n\n\n\n<p>After some investigation I&#8217;ve found this post that seemed to be related to the issue above: <a href=\"https:\/\/github.com\/kubernetes\/minikube\/issues\/14789\">https:\/\/github.com\/kubernetes\/minikube\/issues\/14789<\/a><\/p>\n\n\n\n<p>The issue is that there is a timeout before the image is completely pulled. The workaround is to pull the image manually with the command below:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % minikube ssh docker pull &quot;quay.io\/cilium\/cilium:v1.12.1@sha256:ea2db1ee21b88127b5c18a96ad155c25485d0815a667ef77c2b7c7f31cab601b&quot; -p cluster-cilium\n<\/pre><\/div>\n\n\n<p>I deleted the 3 cilium pods and they came back with the image properly loaded and reached the Running state. I could then run <strong>cilium status<\/strong> in order to validate everything was in order:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % cilium status\n    \/\u00af\u00af\\\n \/\u00af\u00af\\__\/\u00af\u00af\\    Cilium:         OK\n \\__\/\u00af\u00af\\__\/    Operator:       OK\n \/\u00af\u00af\\__\/\u00af\u00af\\    Hubble:         disabled\n \\__\/\u00af\u00af\\__\/    ClusterMesh:    disabled\n    \\__\/\n\nDaemonSet         cilium             Desired: 3, Ready: 3\/3, Available: 3\/3\nDeployment        cilium-operator    Desired: 1, Ready: 1\/1, Available: 1\/1\nContainers:       cilium             Running: 3\n                  cilium-operator    Running: 1\nCluster Pods:     1\/1 managed by Cilium\nImage versions    cilium             quay.io\/cilium\/cilium:v1.12.1@sha256:ea2db1ee21b88127b5c18a96ad155c25485d0815a667ef77c2b7c7f31cab601b: 3\n                  cilium-operator    quay.io\/cilium\/operator-generic:v1.12.1@sha256:93d5aaeda37d59e6c4325ff05030d7b48fabde6576478e3fdbfb9bb4a68ec4a1: 1\n<\/pre><\/div>\n\n\n<p>According to the last comments of the post about this issue less than 2 weeks ago, it should be fixed when minikube is using a different container runtime as containerd but I haven&#8217;t tried it yet.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Last tips<\/h2>\n\n\n\n<p>I&#8217;ve started this post by using 2 clusters in minikube, one for calico and one for cilium. If you want to check <strong>minikube status<\/strong> or install some addons, you need to specify on which cluster you want to do it using the -p flag. Each cluster is called a profile in minikube and you can check them as follows:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % minikube profile list\n|----------------|-----------|---------|--------------|------|---------|---------|-------|--------|\n|    Profile     | VM Driver | Runtime |      IP      | Port | Version | Status  | Nodes | Active |\n|----------------|-----------|---------|--------------|------|---------|---------|-------|--------|\n| cluster-calico | docker    | docker  | 192.168.58.2 | 8443 | v1.24.3 | Running |     2 |        |\n| cluster-cilium | docker    | docker  | 192.168.49.2 | 8443 | v1.24.3 | Running |     3 |        |\n|----------------|-----------|---------|--------------|------|---------|---------|-------|--------|\n<\/pre><\/div>\n\n\n<p>If you want to switch to your calico cluster, just enter the following command:<\/p>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\nenb@DBI-LT-ENB ~ % minikube profile cluster-calico\nminikube profile was successfully set to cluster-calico\n<\/pre><\/div>\n\n\n<p>And use <strong>minikube profile cluster-cilium<\/strong> in order to switch back to your cilium cluster.<\/p>\n\n\n\n<p>That&#8217;s all folks, I hope this post will help you in your testing with minikube and cilium.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this post I&#8217;ll share my experience with installing Cilium in Minikube on my Mac. It was not that hard but I faced an issue I had to troubleshoot. I&#8217;ll also show you how to create several Kubernetes clusters in Minikube in order to have one with Calico as CNI and another one with Cilium [&hellip;]<\/p>\n","protected":false},"author":109,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1320,1522],"tags":[2666,2700,2634,2434],"type_dbi":[],"class_list":["post-18913","post","type-post","status-publish","format-standard","hentry","category-devops","category-kubernetes","tag-calico","tag-cilium","tag-kubernetes-2","tag-minikube"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Cilium installation in Minikube using a multi-cluster environment - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Cilium installation in Minikube using a multi-cluster environment\" \/>\n<meta property=\"og:description\" content=\"In this post I&#8217;ll share my experience with installing Cilium in Minikube on my Mac. It was not that hard but I faced an issue I had to troubleshoot. I&#8217;ll also show you how to create several Kubernetes clusters in Minikube in order to have one with Calico as CNI and another one with Cilium [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-09-23T15:44:53+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-09-23T15:44:54+00:00\" \/>\n<meta name=\"author\" content=\"DevOps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"DevOps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/\"},\"author\":{\"name\":\"DevOps\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735\"},\"headline\":\"Cilium installation in Minikube using a multi-cluster environment\",\"datePublished\":\"2022-09-23T15:44:53+00:00\",\"dateModified\":\"2022-09-23T15:44:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/\"},\"wordCount\":550,\"commentCount\":0,\"keywords\":[\"calico\",\"cilium\",\"kubernetes\",\"minikube\"],\"articleSection\":[\"DevOps\",\"Kubernetes\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/\",\"name\":\"Cilium installation in Minikube using a multi-cluster environment - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2022-09-23T15:44:53+00:00\",\"dateModified\":\"2022-09-23T15:44:54+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Cilium installation in Minikube using a multi-cluster environment\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735\",\"name\":\"DevOps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g\",\"caption\":\"DevOps\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/devops\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Cilium installation in Minikube using a multi-cluster environment - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/","og_locale":"en_US","og_type":"article","og_title":"Cilium installation in Minikube using a multi-cluster environment","og_description":"In this post I&#8217;ll share my experience with installing Cilium in Minikube on my Mac. It was not that hard but I faced an issue I had to troubleshoot. I&#8217;ll also show you how to create several Kubernetes clusters in Minikube in order to have one with Calico as CNI and another one with Cilium [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/","og_site_name":"dbi Blog","article_published_time":"2022-09-23T15:44:53+00:00","article_modified_time":"2022-09-23T15:44:54+00:00","author":"DevOps","twitter_card":"summary_large_image","twitter_misc":{"Written by":"DevOps","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/"},"author":{"name":"DevOps","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735"},"headline":"Cilium installation in Minikube using a multi-cluster environment","datePublished":"2022-09-23T15:44:53+00:00","dateModified":"2022-09-23T15:44:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/"},"wordCount":550,"commentCount":0,"keywords":["calico","cilium","kubernetes","minikube"],"articleSection":["DevOps","Kubernetes"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/","url":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/","name":"Cilium installation in Minikube using a multi-cluster environment - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-09-23T15:44:53+00:00","dateModified":"2022-09-23T15:44:54+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/cilium-installation-in-minikube-using-a-multi-cluster-environment\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Cilium installation in Minikube using a multi-cluster environment"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/4cd1b5f8a3de93f05a16ab8d7d2b7735","name":"DevOps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/cdd2dd7441774355062c0f0f68612296b059cd1e2ff6c7af0b15dba0ed64a85f?s=96&d=mm&r=g","caption":"DevOps"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/devops\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18913","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/109"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=18913"}],"version-history":[{"count":19,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18913\/revisions"}],"predecessor-version":[{"id":19248,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/18913\/revisions\/19248"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=18913"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=18913"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=18913"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=18913"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}