2021/04/13 17:11:23 [INFO] generate received request 2021/04/13 17:11:23 [INFO] received CSR 2021/04/13 17:11:23 [INFO] generating key: ecdsa-256 2021/04/13 17:11:23 [INFO] encoded CSR 2021/04/13 17:11:23 [INFO] 2021/04/13 17:11:24 [INFO] generate received request 2021/04/13 17:11:24 [INFO] received CSR 2021/04/13 17:11:24 [INFO] generating key: ecdsa-256 2021/04/13 17:11:24 [INFO] encoded CSR 2021/04/13 17:11:24 [INFO] "value": "eb3a688b-b3aa-495c-b20a-d4f79e7c088d", "source": "k8s" } ] } ] Revision: 11 It is also possible to monitor the HTTP requests live by using cilium monitor: $ kubectl exec -it

/apis/cilium.io/v2/namespaces/default/ciliumnetworkpolicies/rule1 UID: 837a2f1b-1f0b-11e9-9609-080027702f09 Spec: Endpoint Selector: Match Labels: Class: deathstar Org: /apis/cilium.io/v2/namespaces/default/ciliumnetworkpolicies/rule1 UID: 837a2f1b-1f0b-11e9-9609-080027702f09 Spec: Endpoint Selector: Match Labels: Class: deathstar Org: "source": "k8s" }, { "key": "io.cilium.k8s.policy.uid", "value": "837a2f1b-1f0b-11e9-9609-080027702f09", "source": "k8s" }, { "key": "io.cilium.k8s.policy.namespace"

/apis/cilium.io/v2/namespaces/default/ciliumnetwork UID: 837a2f1b-1f0b-11e9-9609-080027702f09 Spec: Endpoint Selector: Match Labels: Class: deathstar Org: /apis/cilium.io/v2/namespaces/default/ciliumnetwork UID: 837a2f1b-1f0b-11e9-9609-080027702f09 Spec: Endpoint Selector: Match Labels: Class: deathstar "k8s" }, { "key": "io.cilium.k8s.policy.uid", "value": "837a2f1b-1f0b-11e9-9609-080027702f09", "source": "k8s" }, { "key": "io.cilium.k8s.policy

2021/04/13 17:11:23 [INFO] generate received request 2021/04/13 17:11:23 [INFO] received CSR 2021/04/13 17:11:23 [INFO] generating key: ecdsa-256 2021/04/13 17:11:23 [INFO] encoded CSR 2021/04/13 17:11:23 [INFO] 2021/04/13 17:11:24 [INFO] generate received request 2021/04/13 17:11:24 [INFO] received CSR 2021/04/13 17:11:24 [INFO] generating key: ecdsa-256 2021/04/13 17:11:24 [INFO] encoded CSR 2021/04/13 17:11:24 [INFO] "value": "eb3a688b-b3aa-495c-b20a-d4f79e7c088d", "source": "k8s" } ] } ] Revision: 11 It is also possible to monitor the HTTP requests live by using cilium monitor: $ kubectl exec -it

/apis/cilium.io/v2/namespaces/default/ciliumnetworkpolicies/rule1 UID: 837a2f1b-1f0b-11e9-9609-080027702f09 Spec: Endpoint Selector: Match Labels: Class: deathstar Org: /apis/cilium.io/v2/namespaces/default/ciliumnetworkpolicies/rule1 UID: 837a2f1b-1f0b-11e9-9609-080027702f09 Spec: Endpoint Selector: Match Labels: Class: deathstar Org: "source": "k8s" }, { "key": "io.cilium.k8s.policy.uid", "value": "837a2f1b-1f0b-11e9-9609-080027702f09", "source": "k8s" }, { "key": "io.cilium.k8s.policy.namespace"

"value": "eb3a688b-b3aa-495c-b20a-d4f79e7c088d", "source": "k8s" } ] } ] Revision: 11 We hope you enjoyed the tutorial. Feel free to play more with the setup, read the rest of the documentation a855e745-69d8-4159-b8b6-e2bafed8387a | c692ce90-bf57-11e8-98e6- f1a9f45fc4d8 | cee6d956-dbeb-4b09-ad21-1dd93290fa6c | True 5b9a7990-657e-442d-a3f7-94484f06696e | c8493120-bf57-11e8-98e6- f1a9f45fc4d8 | e74a0300-9 53ed94d0-ddac-4b14-8c2f-ba6f83a8218c | c641a150-bf57-11e8-98e6- f1a9f45fc4d8 | 104ddbb6-f2f7-4cd0-8683-cc18cccc1326 | True 074ad3b9-a47d-4ebc-83d3-cad75b1911ce | 9674ed40-bf59-11e8-98e6- f1a9f45fc4d8 | 6ad3139f-e

"value": "eb3a688b-b3aa-495c-b20a-d4f79e7c088d", "source": "k8s" } ] } ] Revision: 11 It is also possible to monitor the HTTP requests live by using cilium monitor: $ kubectl exec -it a855e745-69d8-4159-b8b6-e2bafed8387a | c692ce90-bf57-11e8-98e6- f1a9f45fc4d8 | cee6d956-dbeb-4b09-ad21-1dd93290fa6c | True 5b9a7990-657e-442d-a3f7-94484f06696e | c8493120-bf57-11e8-98e6- f1a9f45fc4d8 | e74a0300-9 53ed94d0-ddac-4b14-8c2f-ba6f83a8218c | c641a150-bf57-11e8-98e6- f1a9f45fc4d8 | 104ddbb6-f2f7-4cd0-8683-cc18cccc1326 | True 074ad3b9-a47d-4ebc-83d3-cad75b1911ce | 9674ed40-bf59-11e8-98e6- f1a9f45fc4d8 | 6ad3139f-e