Case 1: deploy everything into the same namespace created by kubeflow.
- Deploy manifests folder to cluster
kubectl apply -f manifests-same-namespace --recursive - Open a shell into the pod
test-employee-notebookin namespaceaaw-fc - Run
curl -svL -o /dev/null -D - https://edition.cnn.com/politics
Result: the request completes with status code 200 and an access log is recorded in the egress gateway.
Tear down the example with kubectl delete -f manifests-same-namespace --recursive.
Case 2: deploy notebook pod into different namespace (collin-brown), egress gateway into a namespace created by kubeflow (aaw-fc), and add network policies to allow communication between the two namespaces.
- Deploy manifests folder
kubectl apply -f manifests-different-namespace/ --recursive - Open a shell into the
test-employee-notebookpod in namespacecollin-brown - Run
curl -svL -o /dev/null -D - https://edition.cnn.com/politics
Result: the curl request fails with error message OpenSSL SSL_connect: Connection reset by peer in connection to edition.cnn.com:443.
Tear down example with kubectl delete -f manifests-different-namespace/ --recursive
Case 3: deploy notebook pod into different namespace (collin-brown), egress gateway into system namespace (cloud-main-system), and add network policies to allow communication between the two namespaces.
- Deploy manifests folder
kubectl apply -f manifests-different-namespace/ --recursive - Open a shell into the
test-employee-notebookpod in namespacecollin-brown - Run
curl -svL -o /dev/null -D - https://edition.cnn.com/politics
Result: the curl request fails with error message OpenSSL SSL_connect: Connection reset by peer in connection to edition.cnn.com:443.
Tear down example with kubectl delete -f manifests-cloud-main/ --recursive