4/4 If Hubble Relay reports that all nodes are connected, as in the example output above, you can now use the CLI to observe flows of the entire cluster: hubble --server localhost:4245 observe If you For more information about Hubble and its components, see the Observability section. Next steps Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps microk8s Cilium service microk8s enable cilium 3. Cilium is now configured! The cilium CLI is provided as microk8s.cilium. Next steps Now that you have a Kubernetes cluster with Cilium up and running

account. Create an OpenShift OKD Cluster First, set the cluster name: CLUSTER_NAME="cluster-1" Now, create configuration files: Note The sample output below is showing the AWS provider, but it should disableDefaultCNI: true podSubnet: "10.2.0.0/16" serviceSubnet: "10.3.0.0/16" Create Kind Clusters We can now create the respective clusters: kind create cluster --name=cluster1 --config=kind-cluster1.yaml kind cilium.conflist and remove the standard 05-cilium.conf. The new configuration now enables HostPort. Any new pod scheduled is now able to make use of the HostPort functionality. Restart existing pods The

Running 0 75s probe-866bb6f696-tb926 1/1 Running 0 75s Next steps Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps microk8s Cilium service microk8s.enable cilium 3. Cilium is now configured! The cilium CLI is provided as microk8s.cilium. Next steps Now that you have a Kubernetes cluster with Cilium up and running cilium.conflist and remove the standard 05-cilium.conf. The new configuration now enables HostPort. Any new pod scheduled is now able to make use of the HostPort functionality. Restart existing pods The

This is expected since these pods need at least 2 nodes to be scheduled successfully. Next steps Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps microk8s Cilium service microk8s.enable cilium 3. Cilium is now configured! The cilium CLI is provided as microk8s.cilium. Next steps Now that you have a Kubernetes cluster with Cilium up and running Pending state. This is expected since these pods need at least 2 nodes to be scheduled successfully. Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps

Visit Hubble Tutorials [https://github.com/cilium/hubble/blob/v0.5/tutorials/README.md]. Next steps Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps microk8s Cilium service microk8s.enable cilium 3. Cilium is now configured! The cilium CLI is provided as microk8s.cilium. Next steps Now that you have a Kubernetes cluster with Cilium up and running ty.md]. Visit Hubble Tutorials [https://github.com/cilium/hubble/blob/v0.5/tutorials/README.md]. Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps

.5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam Next steps Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps .5/exam kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/exam Next steps Now that you have a Kubernetes cluster with Cilium up and running, you can take a couple of next steps Minikube as the simplest way to set up a Kubernetes cluster with Cilium. Deploy the Demo Application Now that we have Cilium deployed and kube-dns opera�ng correctly we can deploy our demo applica�on. In

account. Create an OpenShift OKD Cluster First, set the cluster name: CLUSTER_NAME="cluster-1" Now, create configuration files: Note The sample output below is showing the AWS provider, but it should disableDefaultCNI: true podSubnet: "10.2.0.0/16" serviceSubnet: "10.3.0.0/16" Create Kind Clusters We can now create the respective clusters: kind create cluster --name=cluster1 --config=kind-cluster1.yaml kind cilium.conflist and remove the standard 05-cilium.conf. The new configuration now enables HostPort. Any new pod scheduled is now able to make use of the HostPort functionality. Restart existing pods The