e/auth/kubeconfig' INFO Access the OpenShift web-console here: https://console-openshift- console.apps.cluster-name.ilya-openshift-test-1.cilium.rocks INFO Login to the console with user: "kubeadmin", catalog: Once added, you should see the Cilium repository in the catalog list: Navigate to the Global Apps list and click the button to Launch an application: Provide a name for the application and select create -f https://raw.githubusercontent.com/cilium/cilium/v1.10/e service/deathstar created deployment.apps/deathstar created pod/tiefighter created pod/xwing created Kubernetes will deploy the pods and service

e/auth/kubeconfig' INFO Access the OpenShift web-console here: https://console-openshift- console.apps.cluster-name.ilya-openshift-test-1.cilium.rocks INFO Login to the console with user: "kubeadmin", catalog: Once added, you should see the Cilium repository in the catalog list: Navigate to the Global Apps list and click the button to Launch an application: Provide a name for the application and select create -f https://raw.githubusercontent.com/cilium/cilium/v1.11/e service/deathstar created deployment.apps/deathstar created pod/tiefighter created pod/xwing created Kubernetes will deploy the pods and service

catalog: Once added, you should see the Cilium repository in the catalog list: Navigate to the Global Apps list and click the button to Launch an application: Provide a name for the application and select configmap/cilium-config patched $ kubectl -n $CILIUM_NAMESPACE rollout restart ds/cilium daemonset.apps/cilium restarted $ kubectl -n kube-system rollout status ds/cilium Waiting for daemon set "cilium" configmap/cilium-config patched $ kubectl -n $CILIUM_NAMESPACE rollout restart ds/cilium daemonset.apps/cilium restarted $ kubectl -n kube-system rollout status ds/cilium Waiting for daemon set "cilium"

catalog: Once added, you should see the Cilium repository in the catalog list: Navigate to the Global Apps list and click the button to Launch an application: Provide a name for the application and select configmap/cilium-config patched $ kubectl -n $CILIUM_NAMESPACE rollout restart ds/cilium daemonset.apps/cilium restarted $ kubectl -n $CILIUM_NAMESPACE rollout status ds/cilium Waiting for daemon set "cilium" configmap/cilium-config patched $ kubectl -n $CILIUM_NAMESPACE rollout restart ds/cilium daemonset.apps/cilium restarted $ kubectl -n kube-system rollout status ds/cilium Waiting for daemon set "cilium"

Cilium installed the service correctly. The following yaml is used for the backend pods: apiVersion: apps/v1 kind: Deployment metadata: name: my-nginx spec: selector: matchLabels: run: my-nginx within a container cluster. We’ll start with an overly simple example where we create two additional apps, app2 and app3, and we want app2 containers to be able to reach app1 containers, but app3 containers particular port. $ curl -i -H 'Content-Type: application/json' -d @web-server.json 127.0.0.1:8080/v2/apps You should see output similar to the following: HTTP/1.1 201 Created ... Marathon-Deployment-Id:

within a container cluster. We’ll start with an overly simple example where we create two additional apps, app2 and app3, and we want app2 containers to be able to reach app1 containers, but app3 containers particular port. $ curl -i -H 'Content-Type: application/json' -d @web-server.json 127.0.0.1:8080/v2/apps You should see output similar to the following: HTTP/1.1 201 Created ... Marathon-Deployment-Id: application/json' -d @goodclient.json 127.0.0.1:8080/v2/apps $ curl -i -H 'Content-Type: application/json' -d @badclient.json 127.0.0.1:8080/v2/apps You can observe the newly created endpoints in Cilium

io/kube-state-metrics created clusterrole.rbac.authorization.k8s.io/kube-state-metrics created deployment.apps/kube-state-metrics created rolebinding.rbac.authorization.k8s.io/kube-state-metrics created role.rbac com/cilium/cilium/v1.5/ex service/kafka created ciliumnetworkpolicy.cilium.io/kafka-authaudit created statefulset.apps/kafka-v1 created Wait un�l the kafka-v1-0 pod is ready, i.e. un�l it has a READY count of 1/1 : within a container cluster. We’ll start with an overly simple example where we create two addi�onal apps, app2 and app3, and we want app2 containers to be able to reach app1 containers, but app3 containers