From 386a311a8841530cfd8d3338e76a8ee672d51243 Mon Sep 17 00:00:00 2001 From: Vahan Koloyan Date: Thu, 21 Mar 2024 13:37:27 +0000 Subject: [PATCH] Revert "Clicable Images" This reverts commit da5bb5a0745590809dd0e48bbbc68e6b4ec6a01d. --- sandbox/Sandbox15/creating-services.rst | 4 ---- sandbox/Sandbox15/onprem-k8s.rst | 8 -------- sandbox/Sandbox15/sandbox-info.rst | 1 + 3 files changed, 1 insertion(+), 12 deletions(-) diff --git a/sandbox/Sandbox15/creating-services.rst b/sandbox/Sandbox15/creating-services.rst index 92016fbf81..19284b9406 100644 --- a/sandbox/Sandbox15/creating-services.rst +++ b/sandbox/Sandbox15/creating-services.rst @@ -145,8 +145,6 @@ In this exercise we will quickly configure an Anycast IP address in the Netris C .. image:: /images/l3lb_srv01.png :align: center - :alt: SRV01 L3LB - :target: ../../_images/l3lb_srv01.png In order to trigger the L3 load balancer to switch directing the traffic towards the other backend server (in this case from **srv01-nyc** to **srv02-nyc**, which based on the unique hash in your situation could be the other way around), we can simulate the unavailability of the backend server we ended up on by putting it in **Maintenance** mode. @@ -163,8 +161,6 @@ In order to trigger the L3 load balancer to switch directing the traffic towards .. image:: /images/l3lb_srv02.png :align: center - :alt: SRV02 L3LB - :target: ../../_images/l3lb_srv02.png More details about AL3LB (Anycast L3 load balancer) can be found on the :ref:`"L3 Load Balancer (Anycast LB)"` page. diff --git a/sandbox/Sandbox15/onprem-k8s.rst b/sandbox/Sandbox15/onprem-k8s.rst index 02841ea966..82ebf5358e 100644 --- a/sandbox/Sandbox15/onprem-k8s.rst +++ b/sandbox/Sandbox15/onprem-k8s.rst @@ -13,8 +13,6 @@ The Sandbox environment offers a pre-existing 3 node Kubernetes cluster deployed .. image:: /images/sandbox-l4lb-kubeapi.png :align: center - :alt: Sandbox L4LB KubeAPI - :target: ../../_images/sandbox-l4lb-kubeapi.png To access the built-in Kubernetes cluster, put the "Kubeconfig" file which you received via the introductory email into your ``~/.kube/config`` or set "KUBECONFIG" environment variable using ``export KUBECONFIG=~/Downloads/config`` on your local machine. Afterwards, try to connect to the k8s cluster: @@ -120,8 +118,6 @@ Going into the Netris Controller web interface, navigate to **Services → L4 Lo .. image:: /images/sandbox-podinfo-prov.png :align: center - :alt: Sandbox PodInfo Provisioning - :target: ../../_images/sandbox-podinfo-prov.png After provisioning has finished, let's one more time look at service in k8s: @@ -171,8 +167,6 @@ Wait a few seconds, you can see the provisioning process on the controller: .. image:: /images/sandbox-podinfo-ready.png :align: center - :alt: Sandbox PodInfo Ready - :target: ../../_images/sandbox-podinfo-ready.png Curl again, without specifying a port: @@ -295,8 +289,6 @@ You can also inspect the L4LB in the Netris Controller web interface: .. image:: /images/sandbox-l4lbs.png :align: center - :alt: Sandbox L4LBs - :target: ../../_images/sandbox-l4lbs.png V-Net Custom Resource --------------------- diff --git a/sandbox/Sandbox15/sandbox-info.rst b/sandbox/Sandbox15/sandbox-info.rst index 4a1c3e64a4..88d7c85c6d 100644 --- a/sandbox/Sandbox15/sandbox-info.rst +++ b/sandbox/Sandbox15/sandbox-info.rst @@ -31,6 +31,7 @@ Topology diagram :target: ../../_images/sandbox_topology_new.png + Netris Controller ================= https://sandbox15.netris.io