From 9c44f14dcac0635ba377be0b2451a6817d5fe517 Mon Sep 17 00:00:00 2001 From: NSMBot Date: Fri, 19 Apr 2024 10:50:03 +0000 Subject: [PATCH] Update references Signed-off-by: NSMBot --- examples/afxdp/README.md | 2 +- examples/basic/README.md | 2 +- .../features/annotated-namespace/README.md | 4 +-- .../features/change-nse-dynamically/README.md | 8 ++--- examples/features/dns/README.md | 2 +- .../Kernel2IP2Kernel_dual_stack/README.md | 2 +- .../Kernel2Kernel_dual_stack/README.md | 2 +- .../dual-stack/vl3-dual-stack/README.md | 4 +-- .../exclude-prefixes-client/README.md | 2 +- examples/features/exclude-prefixes/README.md | 4 +-- .../ipv6/Kernel2IP2Kernel_ipv6/README.md | 2 +- .../ipv6/Kernel2IP2Memif_ipv6/README.md | 2 +- .../ipv6/Kernel2Kernel_ipv6/README.md | 2 +- .../ipv6/Memif2IP2Kernel_ipv6/README.md | 2 +- .../ipv6/Memif2IP2Memif_ipv6/README.md | 2 +- .../features/ipv6/Memif2Memif_ipv6/README.md | 2 +- examples/features/jaeger/README.md | 8 ++--- examples/features/multiple-services/README.md | 2 +- .../features/mutually-aware-nses/README.md | 2 +- examples/features/nse-composition/README.md | 2 +- examples/features/opa/README.md | 2 +- .../features/policy-based-routing/README.md | 2 +- examples/features/scale-from-zero/README.md | 2 +- examples/features/scaled-registry/README.md | 2 +- examples/features/select-forwarder/README.md | 2 +- examples/features/vl3-dns/README.md | 2 +- examples/features/vl3-ipv6/README.md | 2 +- examples/features/vl3-lb/README.md | 2 +- .../features/vl3-scale-from-zero/README.md | 2 +- examples/features/webhook-smartvf/README.md | 2 +- examples/features/webhook/README.md | 2 +- examples/heal/dataplane-interrupt/README.md | 2 +- examples/heal/local-forwarder-death/README.md | 2 +- .../README.md | 2 +- examples/heal/local-nse-death/README.md | 4 +-- .../heal/local-nsm-system-restart/README.md | 4 +-- .../README.md | 2 +- .../local-nsmgr-local-nse-memif/README.md | 4 +-- .../heal/local-nsmgr-remote-nsmgr/README.md | 2 +- examples/heal/local-nsmgr-restart/README.md | 2 +- .../heal/registry-local-endpoint/README.md | 4 +-- .../heal/registry-remote-forwarder/README.md | 2 +- examples/heal/registry-remote-nsmgr/README.md | 2 +- examples/heal/registry-restart/README.md | 4 +-- .../heal/remote-forwarder-death-ip/README.md | 2 +- .../heal/remote-forwarder-death/README.md | 2 +- examples/heal/remote-nse-death-ip/README.md | 4 +-- examples/heal/remote-nse-death/README.md | 4 +-- .../README.md | 4 +-- examples/heal/remote-nsmgr-death/README.md | 8 ++--- .../remote-nsmgr-remote-endpoint/README.md | 4 +-- .../heal/remote-nsmgr-restart-ip/README.md | 2 +- examples/heal/remote-nsmgr-restart/README.md | 2 +- examples/heal/spire-agent-restart/README.md | 2 +- .../heal/spire-server-agent-restart/README.md | 2 +- examples/heal/spire-server-restart/README.md | 2 +- examples/heal/spire-upgrade/README.md | 8 ++--- examples/heal/vl3-nscs-death/README.md | 2 +- examples/heal/vl3-nse-death/README.md | 2 +- .../heal_extended/component-restart/README.md | 2 +- .../basic/README.md | 6 ++-- .../ipsec/README.md | 6 ++-- .../two_cluster_configuration/basic/README.md | 4 +-- .../spiffe_federation/README.md | 4 +-- .../floating_Kernel2Ethernet2Kernel/README.md | 6 ++-- .../floating_Kernel2Ethernet2Memif/README.md | 6 ++-- .../floating_Kernel2IP2Kernel/README.md | 6 ++-- .../floating_Kernel2IP2Memif/README.md | 6 ++-- .../floating_Memif2Ethernet2Kernel/README.md | 6 ++-- .../floating_Memif2Ethernet2Memif/README.md | 6 ++-- .../floating_Memif2IP2Kernel/README.md | 6 ++-- .../floating_Memif2IP2Memif/README.md | 6 ++-- .../usecases/floating_dns/README.md | 6 ++-- .../floating_nse_composition/README.md | 6 ++-- .../usecases/floating_vl3-basic/README.md | 12 ++++---- .../usecases/floating_vl3-dns/README.md | 12 ++++---- .../floating_vl3-scale-from-zero/README.md | 12 ++++---- .../heal_floating-forwarder-death/README.md | 6 ++-- .../heal_floating-nse-death/README.md | 6 ++-- .../heal_floating-nsm-system-death/README.md | 12 ++++---- .../heal_interdomain-nsmgr-death/README.md | 4 +-- .../README.md | 4 +-- .../heal_interdomain-registry-death/README.md | 4 +-- .../README.md | 4 +-- .../interdomain_Kernel2IP2Kernel/README.md | 4 +-- .../usecases/interdomain_dns/README.md | 4 +-- .../interdomain/usecases/nsm_consul/README.md | 30 +++++++++---------- .../usecases/nsm_consul_vl3/README.md | 8 ++--- .../interdomain/usecases/nsm_istio/README.md | 16 +++++----- .../usecases/nsm_istio_booking/README.md | 12 ++++---- .../usecases/nsm_kuma_universal_vl3/README.md | 10 +++---- examples/ipsec_mechanism/README.md | 2 +- examples/k8s_monolith/external_nsc/README.md | 2 +- .../external_nsc/docker/README.md | 2 +- .../external_nsc/spiffe_federation/README.md | 4 +-- .../usecases/Kernel2IP2Kernel/README.md | 2 +- examples/k8s_monolith/external_nse/README.md | 2 +- .../external_nse/docker/README.md | 2 +- .../external_nse/spiffe_federation/README.md | 4 +-- .../usecases/Kernel2IP2Kernel/README.md | 2 +- .../memory/Kernel2Ethernet2Kernel/README.md | 2 +- examples/memory/Kernel2Kernel/README.md | 2 +- examples/memory/Memif2Memif/README.md | 2 +- examples/memory/README.md | 2 +- examples/multiforwarder/README.md | 2 +- examples/multiforwarder_vlantag/README.md | 2 +- examples/observability/dashboard/README.md | 2 +- .../jaeger_and_prometheus/README.md | 4 +-- examples/observability/nsm_system/README.md | 2 +- examples/ovs/README.md | 2 +- examples/pss/README.md | 2 +- examples/pss/use-cases/nginx/README.md | 2 +- examples/remotevlan_ovs/README.md | 2 +- examples/remotevlan_vpp/README.md | 2 +- examples/spire/cluster1/README.md | 6 ++-- examples/spire/cluster2/README.md | 6 ++-- examples/spire/cluster3/README.md | 6 ++-- examples/spire/single_cluster/README.md | 6 ++-- examples/spire/single_cluster_csi/README.md | 6 ++-- examples/sriov/README.md | 2 +- examples/sriov_vlantag/README.md | 2 +- .../Kernel2Ethernet2Kernel/README.md | 2 +- .../README.md | 2 +- .../README.md | 2 +- .../use-cases/Kernel2Ethernet2Memif/README.md | 2 +- examples/use-cases/Kernel2IP2Kernel/README.md | 2 +- examples/use-cases/Kernel2IP2Memif/README.md | 2 +- examples/use-cases/Kernel2Kernel/README.md | 2 +- .../use-cases/Kernel2KernelVLAN/README.md | 2 +- .../Kernel2Kernel_Vfio2Noop/README.md | 2 +- .../Kernel2Kernel_Vfio2NoopVlanTag/README.md | 2 +- examples/use-cases/Kernel2Memif/README.md | 2 +- .../use-cases/Kernel2RVlanBreakout/README.md | 2 +- .../use-cases/Kernel2RVlanInternal/README.md | 2 +- .../use-cases/Kernel2RVlanMultiNS/README.md | 10 +++---- .../use-cases/Memif2Ethernet2Kernel/README.md | 2 +- .../use-cases/Memif2Ethernet2Memif/README.md | 2 +- examples/use-cases/Memif2IP2Kernel/README.md | 2 +- examples/use-cases/Memif2IP2Memif/README.md | 2 +- examples/use-cases/Memif2Kernel/README.md | 2 +- examples/use-cases/Memif2Memif/README.md | 2 +- examples/use-cases/SmartVF2SmartVF/README.md | 2 +- examples/use-cases/SriovKernel2Noop/README.md | 4 +-- .../SriovKernel2NoopVlanTag/README.md | 4 +-- examples/use-cases/Vfio2Noop/README.md | 2 +- examples/use-cases/Vfio2NoopVlanTag/README.md | 2 +- examples/use-cases/vl3-basic/README.md | 2 +- to-ref.sh | 4 +-- 148 files changed, 281 insertions(+), 281 deletions(-) diff --git a/examples/afxdp/README.md b/examples/afxdp/README.md index 542a235aa481..3d2a60043741 100644 --- a/examples/afxdp/README.md +++ b/examples/afxdp/README.md @@ -21,7 +21,7 @@ If the packet belongs to the NSM interface it forwards it to the VPP, otherwise Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/afxdp?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/afxdp?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/basic/README.md b/examples/basic/README.md index ec87a1c77528..350810073094 100644 --- a/examples/basic/README.md +++ b/examples/basic/README.md @@ -11,7 +11,7 @@ Contain basic setup for NSM that includes `nsmgr`, `forwarder-vpp`, `registry-k8 Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/features/annotated-namespace/README.md b/examples/features/annotated-namespace/README.md index 16ec3eb0ce42..0be8a96fb259 100644 --- a/examples/features/annotated-namespace/README.md +++ b/examples/features/annotated-namespace/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Create test namespace and deploy NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/annotated-namespace?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/annotated-namespace?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for NSE to be ready: @@ -28,7 +28,7 @@ kubectl annotate ns ns-annotated-namespace networkservicemesh.io=kernel://annota Apply client patch: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/features/annotated-namespace/client.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/features/annotated-namespace/client.yaml ``` Wait for client to be ready: diff --git a/examples/features/change-nse-dynamically/README.md b/examples/features/change-nse-dynamically/README.md index adb21e051db2..c50a1557bc9e 100644 --- a/examples/features/change-nse-dynamically/README.md +++ b/examples/features/change-nse-dynamically/README.md @@ -10,11 +10,11 @@ Make sure that you have completed steps from [basic](../../basic) or [ipsec mech Deploy NSC and two NSEs: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/change-nse-dynamically?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/change-nse-dynamically?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/features/change-nse-dynamically/blue-netsvc.yaml ``` Wait for applications ready: @@ -40,7 +40,7 @@ kubectl exec pods/blue-nse -n ns-change-nse-dynamically -- ping -c 4 172.16.2.10 Change network service to select green endpoint: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/features/change-nse-dynamically/green-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/features/change-nse-dynamically/green-netsvc.yaml ``` Ping from NSC to the green NSE: @@ -55,7 +55,7 @@ kubectl exec pods/green-nse -n ns-change-nse-dynamically -- ping -c 4 172.16.1.1 Change network service to select blue endpoint: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/features/change-nse-dynamically/blue-netsvc.yaml ``` Ping from NSC to the blue NSE: diff --git a/examples/features/dns/README.md b/examples/features/dns/README.md index 13058517b9ca..0616cb9e5837 100644 --- a/examples/features/dns/README.md +++ b/examples/features/dns/README.md @@ -11,7 +11,7 @@ Make sure that you have completed steps from [features](../) Deploy alpine and nse ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dns?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dns?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack/README.md b/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack/README.md index b6967f7421b5..5a250defac76 100644 --- a/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack/README.md +++ b/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack/README.md @@ -9,7 +9,7 @@ Forwarders are using the `wireguard` mechanism to connect with each other. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/dual-stack/Kernel2Kernel_dual_stack/README.md b/examples/features/dual-stack/Kernel2Kernel_dual_stack/README.md index 6e80ac168392..1f9f68a462cf 100644 --- a/examples/features/dual-stack/Kernel2Kernel_dual_stack/README.md +++ b/examples/features/dual-stack/Kernel2Kernel_dual_stack/README.md @@ -9,7 +9,7 @@ NSC and NSE are using the `kernel` mechanism to connect to its local forwarder. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2Kernel_dual_stack?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2Kernel_dual_stack?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/dual-stack/vl3-dual-stack/README.md b/examples/features/dual-stack/vl3-dual-stack/README.md index e9ee7667f573..a00849788836 100644 --- a/examples/features/dual-stack/vl3-dual-stack/README.md +++ b/examples/features/dual-stack/vl3-dual-stack/README.md @@ -13,8 +13,8 @@ Diagram: Deploy network service, nsc and vl3 nses (See at `kustomization.yaml`): ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack?ref=2937754b2d39bb47f94059b501c6555c8b146f03 -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for clients to be ready: diff --git a/examples/features/exclude-prefixes-client/README.md b/examples/features/exclude-prefixes-client/README.md index 81ec16d298fc..ba0b5ceda6c1 100644 --- a/examples/features/exclude-prefixes-client/README.md +++ b/examples/features/exclude-prefixes-client/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC, services and NSEs: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes-client?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes-client?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/exclude-prefixes/README.md b/examples/features/exclude-prefixes/README.md index dd3ab7927113..98dbc141ec9e 100644 --- a/examples/features/exclude-prefixes/README.md +++ b/examples/features/exclude-prefixes/README.md @@ -12,12 +12,12 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Create config map with excluded prefixes ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes/configmap?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes/configmap?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md index dd5060ea857a..4263cf8e44f4 100644 --- a/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md +++ b/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md @@ -9,7 +9,7 @@ Forwarders are using the `wireguard` mechanism to connect with each other. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Kernel_ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Kernel_ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md index e876059f0ea2..7d1e4c0e146a 100644 --- a/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md +++ b/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md @@ -10,7 +10,7 @@ Forwarders are using the `wireguard` mechanism to connect with each other. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Memif_ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Memif_ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2Kernel_ipv6/README.md index fa1c29a92b5a..3f3a2f748c08 100644 --- a/examples/features/ipv6/Kernel2Kernel_ipv6/README.md +++ b/examples/features/ipv6/Kernel2Kernel_ipv6/README.md @@ -9,7 +9,7 @@ NSC and NSE are using the `kernel` mechanism to connect to its local forwarder. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2Kernel_ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2Kernel_ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md index 8ee7e43022ed..182d30cb370a 100644 --- a/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md +++ b/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md @@ -11,7 +11,7 @@ Forwarders are using the `wireguard` mechanism to connect with each other. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Kernel_ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Kernel_ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md b/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md index 20f1e83dea08..ba7961128a86 100644 --- a/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md +++ b/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md @@ -9,7 +9,7 @@ Forwarders are using the `wireguard` mechanism to connect with each other. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Memif_ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Memif_ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2Memif_ipv6/README.md b/examples/features/ipv6/Memif2Memif_ipv6/README.md index acc65fafdf2c..0226acd2e236 100644 --- a/examples/features/ipv6/Memif2Memif_ipv6/README.md +++ b/examples/features/ipv6/Memif2Memif_ipv6/README.md @@ -8,7 +8,7 @@ NSC and NSE are using the `memif` mechanism to connect to its local forwarder. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2Memif_ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2Memif_ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/jaeger/README.md b/examples/features/jaeger/README.md index dab73d6df5b4..aa67f4d00a32 100644 --- a/examples/features/jaeger/README.md +++ b/examples/features/jaeger/README.md @@ -84,7 +84,7 @@ kubectl wait -n observability --timeout=1m --for=condition=ready pod -l name=jae Apply Jaeger pod: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/jaeger?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/jaeger?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for Jaeger pod status ready: @@ -94,12 +94,12 @@ kubectl wait -n observability --timeout=1m --for=condition=ready pod -l app=jaeg Apply OpenTelemetry pod: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/opentelemetry?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/opentelemetry?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Apply Spire deployments (required for NSM system) ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for Spire pods status ready: @@ -117,7 +117,7 @@ kubectl create ns nsm-system Apply NSM resources: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/nsm-system?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/nsm-system?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/features/multiple-services/README.md b/examples/features/multiple-services/README.md index 72cc962d7436..9c68f95cc46a 100644 --- a/examples/features/multiple-services/README.md +++ b/examples/features/multiple-services/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [ipsec mech Deploy NSC and and two NSEs: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/multiple-services?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/multiple-services?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/mutually-aware-nses/README.md b/examples/features/mutually-aware-nses/README.md index a82fcbeb9d80..327a0e03aa77 100644 --- a/examples/features/mutually-aware-nses/README.md +++ b/examples/features/mutually-aware-nses/README.md @@ -14,7 +14,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/mutually-aware-nses?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/mutually-aware-nses?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/nse-composition/README.md b/examples/features/nse-composition/README.md index 5d5a6f725557..f465f8326141 100644 --- a/examples/features/nse-composition/README.md +++ b/examples/features/nse-composition/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/nse-composition?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/nse-composition?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/opa/README.md b/examples/features/opa/README.md index 5627e9daff95..e5150ff5e6eb 100644 --- a/examples/features/opa/README.md +++ b/examples/features/opa/README.md @@ -19,7 +19,7 @@ Expected that Endpoint(in this case NSMgr) will fail the Request from the client Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/opa?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/opa?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/policy-based-routing/README.md b/examples/features/policy-based-routing/README.md index 6ea4366b8d89..205710472c5c 100644 --- a/examples/features/policy-based-routing/README.md +++ b/examples/features/policy-based-routing/README.md @@ -14,7 +14,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/policy-based-routing?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/policy-based-routing?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/scale-from-zero/README.md b/examples/features/scale-from-zero/README.md index 39a92c400e4e..6fd491ed0131 100644 --- a/examples/features/scale-from-zero/README.md +++ b/examples/features/scale-from-zero/README.md @@ -20,7 +20,7 @@ thus saving cluster resources (see step 14). Deploy NSC and supplier: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scale-from-zero?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scale-from-zero?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/scaled-registry/README.md b/examples/features/scaled-registry/README.md index 254768781c52..a01312fe3cbd 100644 --- a/examples/features/scaled-registry/README.md +++ b/examples/features/scaled-registry/README.md @@ -11,7 +11,7 @@ Make sure that you have completed steps from [basic](../../basic) setup. Deploy NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scaled-registry?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scaled-registry?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for NSE to be ready: diff --git a/examples/features/select-forwarder/README.md b/examples/features/select-forwarder/README.md index 16832bb2b001..5336ad379b3c 100644 --- a/examples/features/select-forwarder/README.md +++ b/examples/features/select-forwarder/README.md @@ -18,7 +18,7 @@ Make sure that you have completed steps from [basic](../../basic) setup. Apply example resources: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/select-forwarder?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/select-forwarder?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/vl3-dns/README.md b/examples/features/vl3-dns/README.md index c5bc3ef16079..d092f856aefe 100644 --- a/examples/features/vl3-dns/README.md +++ b/examples/features/vl3-dns/README.md @@ -27,7 +27,7 @@ The template could be changed via env variable of [cmd-nse-vl3-vpp](../../../app Deploy network service, nsc and vl3 nses (See at `kustomization.yaml`): ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-dns?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-dns?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for clients to be ready: diff --git a/examples/features/vl3-ipv6/README.md b/examples/features/vl3-ipv6/README.md index a31120bd562a..9f2eb6b5dbf8 100644 --- a/examples/features/vl3-ipv6/README.md +++ b/examples/features/vl3-ipv6/README.md @@ -15,7 +15,7 @@ Diagram: Deploy network service, nsc and vl3 nses (See at `kustomization.yaml`): ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-ipv6?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-ipv6?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for clients to be ready: diff --git a/examples/features/vl3-lb/README.md b/examples/features/vl3-lb/README.md index db2d2e32cd5e..b3b0e190bb4d 100644 --- a/examples/features/vl3-lb/README.md +++ b/examples/features/vl3-lb/README.md @@ -56,7 +56,7 @@ When the http request reaches the balancer, it converts the destination address Deploy the vL3 network service, vL3-NSE, vL3-LB, finance-servers and finance-client (the last 3 are actually clients of the vL3 network) (see `kustomization.yaml`): ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-lb?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-lb?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for vL3-clients to be ready: diff --git a/examples/features/vl3-scale-from-zero/README.md b/examples/features/vl3-scale-from-zero/README.md index 81bcd23c5bcb..923f8208b39a 100644 --- a/examples/features/vl3-scale-from-zero/README.md +++ b/examples/features/vl3-scale-from-zero/README.md @@ -9,7 +9,7 @@ allowing the best performance for connectivity. Deploy NSC and supplier: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-scale-from-zero?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-scale-from-zero?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/webhook-smartvf/README.md b/examples/features/webhook-smartvf/README.md index e3da10db9b41..386b1ee85c6d 100644 --- a/examples/features/webhook-smartvf/README.md +++ b/examples/features/webhook-smartvf/README.md @@ -18,7 +18,7 @@ kubectl wait --for=condition=ready --timeout=1m pod ${WH} -n nsm-system Deploy postgres-nsc and postgres-nse ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook-smartvf?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook-smartvf?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/features/webhook/README.md b/examples/features/webhook/README.md index b914d2296cdb..c422c8e2b0c0 100644 --- a/examples/features/webhook/README.md +++ b/examples/features/webhook/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [features](../) Deploy client and nginx-nse ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/dataplane-interrupt/README.md b/examples/heal/dataplane-interrupt/README.md index bd5da495a2a3..cf39aad56da4 100644 --- a/examples/heal/dataplane-interrupt/README.md +++ b/examples/heal/dataplane-interrupt/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/dataplane-interrupt?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/dataplane-interrupt?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/local-forwarder-death/README.md b/examples/heal/local-forwarder-death/README.md index 10786afa1a49..8f5d37be4c02 100644 --- a/examples/heal/local-forwarder-death/README.md +++ b/examples/heal/local-forwarder-death/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/local-forwarder-remote-forwarder/README.md b/examples/heal/local-forwarder-remote-forwarder/README.md index ff0204cfcbd8..1b557db6c1fd 100644 --- a/examples/heal/local-forwarder-remote-forwarder/README.md +++ b/examples/heal/local-forwarder-remote-forwarder/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) setup. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-remote-forwarder?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-remote-forwarder?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/local-nse-death/README.md b/examples/heal/local-nse-death/README.md index 2511ea4d1779..4c5172949ece 100644 --- a/examples/heal/local-nse-death/README.md +++ b/examples/heal/local-nse-death/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-before-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-before-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -44,7 +44,7 @@ kubectl exec pods/alpine -n ns-local-nse-death -- ping -c 4 172.16.1.100 -I 172. Apply patch: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-after-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-after-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Restore NSE pod: diff --git a/examples/heal/local-nsm-system-restart/README.md b/examples/heal/local-nsm-system-restart/README.md index a897e4602b10..bec169d3b492 100644 --- a/examples/heal/local-nsm-system-restart/README.md +++ b/examples/heal/local-nsm-system-restart/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic). Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsm-system-restart?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsm-system-restart?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -39,7 +39,7 @@ kubectl delete mutatingwebhookconfiguration nsm-mutating-webhook kubectl delete ns nsm-system ``` ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Ping from NSC to NSE: diff --git a/examples/heal/local-nsmgr-local-forwarder-memif/README.md b/examples/heal/local-nsmgr-local-forwarder-memif/README.md index 0b6d86a9bffe..6abd676e77b2 100644 --- a/examples/heal/local-nsmgr-local-forwarder-memif/README.md +++ b/examples/heal/local-nsmgr-local-forwarder-memif/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-forwarder-memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-forwarder-memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/local-nsmgr-local-nse-memif/README.md b/examples/heal/local-nsmgr-local-nse-memif/README.md index 58fb51fa8a1f..e112394cd0e7 100644 --- a/examples/heal/local-nsmgr-local-nse-memif/README.md +++ b/examples/heal/local-nsmgr-local-nse-memif/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-before-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-before-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -57,7 +57,7 @@ Restart local NSMgr and NSE: kubectl delete pod ${NSMGR} -n nsm-system ``` ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-after-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-after-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Waiting for new ones: diff --git a/examples/heal/local-nsmgr-remote-nsmgr/README.md b/examples/heal/local-nsmgr-remote-nsmgr/README.md index 97b79847097d..dfca7ba19e5e 100644 --- a/examples/heal/local-nsmgr-remote-nsmgr/README.md +++ b/examples/heal/local-nsmgr-remote-nsmgr/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-remote-nsmgr?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-remote-nsmgr?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/local-nsmgr-restart/README.md b/examples/heal/local-nsmgr-restart/README.md index 04152805708d..9ff70578efa9 100644 --- a/examples/heal/local-nsmgr-restart/README.md +++ b/examples/heal/local-nsmgr-restart/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-restart?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-restart?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/registry-local-endpoint/README.md b/examples/heal/registry-local-endpoint/README.md index 50d891e56620..e85bd387f0cd 100644 --- a/examples/heal/registry-local-endpoint/README.md +++ b/examples/heal/registry-local-endpoint/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-first?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-first?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -45,7 +45,7 @@ kubectl delete pod ${REGISTRY} -n nsm-system Restart NSE. This command recreates NSE with a new label: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-second?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-second?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Waiting for new ones: diff --git a/examples/heal/registry-remote-forwarder/README.md b/examples/heal/registry-remote-forwarder/README.md index 0caa37c78cc8..5337cbbf0875 100644 --- a/examples/heal/registry-remote-forwarder/README.md +++ b/examples/heal/registry-remote-forwarder/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-forwarder?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-forwarder?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/registry-remote-nsmgr/README.md b/examples/heal/registry-remote-nsmgr/README.md index c8b1e972dfdd..60fe86eecf80 100644 --- a/examples/heal/registry-remote-nsmgr/README.md +++ b/examples/heal/registry-remote-nsmgr/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-nsmgr?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-nsmgr?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/registry-restart/README.md b/examples/heal/registry-restart/README.md index d23b03312d70..a3068fd09879 100644 --- a/examples/heal/registry-restart/README.md +++ b/examples/heal/registry-restart/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-before-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-before-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -56,7 +56,7 @@ kubectl wait --for=condition=ready --timeout=1m pod -l app=registry -n nsm-syste Apply a new client: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-after-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-after-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for a new NSC to start: diff --git a/examples/heal/remote-forwarder-death-ip/README.md b/examples/heal/remote-forwarder-death-ip/README.md index cd433b708c29..b2e8a594dbb1 100644 --- a/examples/heal/remote-forwarder-death-ip/README.md +++ b/examples/heal/remote-forwarder-death-ip/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death-ip?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death-ip?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/remote-forwarder-death/README.md b/examples/heal/remote-forwarder-death/README.md index 7ce9411c9b90..09160919a1d4 100644 --- a/examples/heal/remote-forwarder-death/README.md +++ b/examples/heal/remote-forwarder-death/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/remote-nse-death-ip/README.md b/examples/heal/remote-nse-death-ip/README.md index 42274a8aa7de..f1a4f586d797 100644 --- a/examples/heal/remote-nse-death-ip/README.md +++ b/examples/heal/remote-nse-death-ip/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-before-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-before-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -36,7 +36,7 @@ kubectl exec deployments/nse-kernel -n ns-remote-nse-death-ip -- ping -c 4 172.1 Apply patch. It recreates NSE with a new label: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-after-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-after-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for new NSE to start: diff --git a/examples/heal/remote-nse-death/README.md b/examples/heal/remote-nse-death/README.md index 86b8f37cc289..d4242e7cd7e6 100644 --- a/examples/heal/remote-nse-death/README.md +++ b/examples/heal/remote-nse-death/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-before-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-before-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -44,7 +44,7 @@ kubectl exec deployments/nse-kernel -n ns-remote-nse-death -- ping -c 4 172.16.1 Apply patch. It recreates NSE with a new label: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-after-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-after-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for new NSE to start: diff --git a/examples/heal/remote-nsm-system-restart-memif-ip/README.md b/examples/heal/remote-nsm-system-restart-memif-ip/README.md index c2fe6dc0e4f4..966ea1f7f1a3 100644 --- a/examples/heal/remote-nsm-system-restart-memif-ip/README.md +++ b/examples/heal/remote-nsm-system-restart-memif-ip/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic). Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsm-system-restart-memif-ip?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsm-system-restart-memif-ip?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -47,7 +47,7 @@ kubectl delete ns nsm-system kubectl create ns nsm-system ``` ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Ping from NSC to NSE: diff --git a/examples/heal/remote-nsmgr-death/README.md b/examples/heal/remote-nsmgr-death/README.md index 6099103dda48..6c203cd752ce 100644 --- a/examples/heal/remote-nsmgr-death/README.md +++ b/examples/heal/remote-nsmgr-death/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/remote-nse?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/remote-nse?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -36,12 +36,12 @@ kubectl exec deployments/nse-kernel -n ns-remote-nsmgr-death -- ping -c 4 172.16 Kill remote NSMgr: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/nsmgr-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/nsmgr-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Start local NSE instead of the remote one: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/local-nse?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/local-nse?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for the new NSE to start: @@ -68,7 +68,7 @@ kubectl exec ${NEW_NSE} -n ns-remote-nsmgr-death -- ping -c 4 172.16.1.103 Restore NSMgr setup: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/nsmgr?ref=2937754b2d39bb47f94059b501c6555c8b146f03 -n nsm-system +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/nsmgr?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb -n nsm-system ``` Delete ns: diff --git a/examples/heal/remote-nsmgr-remote-endpoint/README.md b/examples/heal/remote-nsmgr-remote-endpoint/README.md index d46e3cd10c9c..ec67ae6cea14 100644 --- a/examples/heal/remote-nsmgr-remote-endpoint/README.md +++ b/examples/heal/remote-nsmgr-remote-endpoint/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-before-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-before-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -49,7 +49,7 @@ Restart remote NSMgr and NSE: kubectl delete pod ${NSMGR} -n nsm-system ``` ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-after-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-after-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Waiting for new ones: diff --git a/examples/heal/remote-nsmgr-restart-ip/README.md b/examples/heal/remote-nsmgr-restart-ip/README.md index 7bb26ccf4e41..e14df91b8367 100644 --- a/examples/heal/remote-nsmgr-restart-ip/README.md +++ b/examples/heal/remote-nsmgr-restart-ip/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart-ip?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart-ip?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/remote-nsmgr-restart/README.md b/examples/heal/remote-nsmgr-restart/README.md index 01f15779fe7f..fd0771dcf7e5 100644 --- a/examples/heal/remote-nsmgr-restart/README.md +++ b/examples/heal/remote-nsmgr-restart/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/spire-agent-restart/README.md b/examples/heal/spire-agent-restart/README.md index e0ef36e04f37..9f09c8045e66 100644 --- a/examples/heal/spire-agent-restart/README.md +++ b/examples/heal/spire-agent-restart/README.md @@ -18,7 +18,7 @@ kubectl create ns ns-spire-agent-restart Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-agent-restart?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-agent-restart?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/spire-server-agent-restart/README.md b/examples/heal/spire-server-agent-restart/README.md index 62bceeb8c41c..5c952df0c9de 100644 --- a/examples/heal/spire-server-agent-restart/README.md +++ b/examples/heal/spire-server-agent-restart/README.md @@ -18,7 +18,7 @@ kubectl create ns ns-spire-server-agent-restart Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-agent-restart?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-agent-restart?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/spire-server-restart/README.md b/examples/heal/spire-server-restart/README.md index 1cc36a053014..5ccdf189ee30 100644 --- a/examples/heal/spire-server-restart/README.md +++ b/examples/heal/spire-server-restart/README.md @@ -18,7 +18,7 @@ kubectl create ns ns-spire-server-restart Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-restart?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-restart?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/heal/spire-upgrade/README.md b/examples/heal/spire-upgrade/README.md index 35c5b0a77030..081c478ebbb4 100644 --- a/examples/heal/spire-upgrade/README.md +++ b/examples/heal/spire-upgrade/README.md @@ -18,7 +18,7 @@ kubectl create ns ns-spire-upgrade Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-upgrade?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-upgrade?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -49,7 +49,7 @@ kubectl delete ns spire Deploy SPIRE and wait for SPIRE server and agents: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash @@ -61,11 +61,11 @@ kubectl wait --for=condition=ready --timeout=1m pod -l app=spire-agent -n spire Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` Ping from NSC to NSE: diff --git a/examples/heal/vl3-nscs-death/README.md b/examples/heal/vl3-nscs-death/README.md index c8324c7f5555..c41038583f7e 100644 --- a/examples/heal/vl3-nscs-death/README.md +++ b/examples/heal/vl3-nscs-death/README.md @@ -7,7 +7,7 @@ This example shows vl3-network recovery after redeploying all clients. Deploy nsc and vl3 nses: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nscs-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nscs-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for clients to be ready: diff --git a/examples/heal/vl3-nse-death/README.md b/examples/heal/vl3-nse-death/README.md index b9faf8409347..5f25e5e5de0c 100644 --- a/examples/heal/vl3-nse-death/README.md +++ b/examples/heal/vl3-nse-death/README.md @@ -7,7 +7,7 @@ This example shows vl3-network recovery after one of the vl3-nse death. Deploy nsc and vl3 nses: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nse-death?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nse-death?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for clients to be ready: diff --git a/examples/heal_extended/component-restart/README.md b/examples/heal_extended/component-restart/README.md index d645323a4915..528ea7647c99 100644 --- a/examples/heal_extended/component-restart/README.md +++ b/examples/heal_extended/component-restart/README.md @@ -15,7 +15,7 @@ Make sure that you have completed steps from [basic](../../basic) setup. Deploy NSCs and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal_extended/component-restart?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal_extended/component-restart?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/three_cluster_configuration/basic/README.md b/examples/interdomain/three_cluster_configuration/basic/README.md index a7f6888ece61..e03b9c9019de 100644 --- a/examples/interdomain/three_cluster_configuration/basic/README.md +++ b/examples/interdomain/three_cluster_configuration/basic/README.md @@ -16,17 +16,17 @@ In this example, NSM-system is deployed on three clusters. The third cluster is Apply NSM resources for cluster1: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Apply NSM resources for cluster2: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Apply NSM resources for cluster3: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for nsmgr-proxy-service exposing: diff --git a/examples/interdomain/three_cluster_configuration/ipsec/README.md b/examples/interdomain/three_cluster_configuration/ipsec/README.md index dd78632ba27d..6e6f68cadb08 100644 --- a/examples/interdomain/three_cluster_configuration/ipsec/README.md +++ b/examples/interdomain/three_cluster_configuration/ipsec/README.md @@ -19,7 +19,7 @@ Prioritize IPSec over other remote mechanisms Apply NSM resources for basic tests: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for nsmgr-proxy-service exposing: @@ -38,7 +38,7 @@ kubectl --kubeconfig=$KUBECONFIG1 wait --for=condition=ready --timeout=1m pod ${ Apply NSM resources for basic tests: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for nsmgr-proxy-service exposing: @@ -57,7 +57,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod ${ Apply NSM resources for basic tests: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for nsmgr-proxy-service exposing: diff --git a/examples/interdomain/two_cluster_configuration/basic/README.md b/examples/interdomain/two_cluster_configuration/basic/README.md index 06fee522b22b..69a658e3e05c 100644 --- a/examples/interdomain/two_cluster_configuration/basic/README.md +++ b/examples/interdomain/two_cluster_configuration/basic/README.md @@ -16,13 +16,13 @@ In this example, NSM-system is deployed on two clusters. Apply NSM resources for cluster1: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Apply NSM resources for cluster2: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for NSM admission webhook on cluster 1: diff --git a/examples/interdomain/two_cluster_configuration/spiffe_federation/README.md b/examples/interdomain/two_cluster_configuration/spiffe_federation/README.md index b838d0185911..18b298ff8e79 100644 --- a/examples/interdomain/two_cluster_configuration/spiffe_federation/README.md +++ b/examples/interdomain/two_cluster_configuration/spiffe_federation/README.md @@ -11,12 +11,12 @@ Once federation is bootstrapped, the trust bundle updates are fetched through th Apply the ClusterSPIFFEID CR for the first cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster1-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster1-spiffeid-template.yaml ``` Apply the ClusterSPIFFEID CR for the second cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster2-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster2-spiffeid-template.yaml ``` Get and store bundles for clusters: diff --git a/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/README.md b/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/README.md index afad3569e664..eb88318113c0 100644 --- a/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/README.md +++ b/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/README.md @@ -18,14 +18,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -37,7 +37,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md index 821e9fe07a64..2f27ab11976e 100644 --- a/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md +++ b/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md @@ -20,14 +20,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -39,7 +39,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=2m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md index 19bc891e5acb..33cc748564c0 100644 --- a/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md +++ b/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md @@ -21,14 +21,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -40,7 +40,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md index a322f6978cbd..15ac1ddab19b 100644 --- a/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md +++ b/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md @@ -22,14 +22,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -41,7 +41,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=2m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md index 1656bd33635d..7987dcd878ab 100644 --- a/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md +++ b/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md @@ -22,14 +22,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -41,7 +41,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md index e9513feb3c99..d793b2ec210d 100644 --- a/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md +++ b/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md @@ -19,14 +19,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -38,7 +38,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=2m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md index 146a0c690847..3b47dd88d6ad 100644 --- a/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md +++ b/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md @@ -22,14 +22,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -41,7 +41,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md b/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md index 84e7dc277e56..16054ca04b5b 100644 --- a/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md +++ b/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md @@ -20,14 +20,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -39,7 +39,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=2m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_dns/README.md b/examples/interdomain/usecases/floating_dns/README.md index 6950bd76b932..0ba0aa317142 100644 --- a/examples/interdomain/usecases/floating_dns/README.md +++ b/examples/interdomain/usecases/floating_dns/README.md @@ -14,21 +14,21 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NetworkService: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **3. Deploy client on cluster1** Deploy client: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_nse_composition/README.md b/examples/interdomain/usecases/floating_nse_composition/README.md index 5b4c08757088..e12fd644ca36 100644 --- a/examples/interdomain/usecases/floating_nse_composition/README.md +++ b/examples/interdomain/usecases/floating_nse_composition/README.md @@ -28,14 +28,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoints on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -47,7 +47,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_vl3-basic/README.md b/examples/interdomain/usecases/floating_vl3-basic/README.md index 203a5a96219d..78b2226ae68f 100644 --- a/examples/interdomain/usecases/floating_vl3-basic/README.md +++ b/examples/interdomain/usecases/floating_vl3-basic/README.md @@ -35,17 +35,17 @@ Start **vl3 ipam** and register **vl3 network service** in the *floating domain* Note: *By default ipam prefix is `172.16.0.0/16` and client prefix len is `24`. We also have two vl3 nses in this example. So we expect to have two vl3 addresses: `172.16.0.0` and `172.16.1.0` that should be accessible by each client.* ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Deploy a vl3-NSE and a client on the cluster1: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Deploy a vl3-NSE and a client on the cluster2: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Wait for clients to be ready** @@ -89,15 +89,15 @@ kubectl --kubeconfig=$KUBECONFIG2 exec pods/alpine -n ns-floating-vl3-basic -- p Cleanup floating domain: ```bash -kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` diff --git a/examples/interdomain/usecases/floating_vl3-dns/README.md b/examples/interdomain/usecases/floating_vl3-dns/README.md index b56db3f661d2..63f2e894160d 100644 --- a/examples/interdomain/usecases/floating_vl3-dns/README.md +++ b/examples/interdomain/usecases/floating_vl3-dns/README.md @@ -16,13 +16,13 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Note: *By default ipam prefix is `172.16.0.0/16` and client prefix len is `24`. We also have two vl3 nses in this example. So we expect to have two vl3 addresses: `172.16.0.0` and `172.16.1.0` that should be accessible by each client.* ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` 1.2. Deploy a vl3-NSE and a client on the cluster1: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash kubectl --kubeconfig=$KUBECONFIG1 wait --for=condition=ready --timeout=5m pod -l app=alpine -n ns-floating-vl3-dns @@ -31,7 +31,7 @@ kubectl --kubeconfig=$KUBECONFIG1 wait --for=condition=ready --timeout=5m pod -l 1.3. Deploy a vl3-NSE and a client on the cluster2: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=5m pod -l app=alpine -n ns-floating-vl3-dns @@ -87,15 +87,15 @@ kubectl --kubeconfig=$KUBECONFIG2 exec pods/alpine-2 -n ns-floating-vl3-dns -- p 1. Cleanup floating domain: ```bash -kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` 2. Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` 3. Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` diff --git a/examples/interdomain/usecases/floating_vl3-scale-from-zero/README.md b/examples/interdomain/usecases/floating_vl3-scale-from-zero/README.md index 68fbb7111664..8ad1453e1aa4 100644 --- a/examples/interdomain/usecases/floating_vl3-scale-from-zero/README.md +++ b/examples/interdomain/usecases/floating_vl3-scale-from-zero/README.md @@ -20,17 +20,17 @@ Start **vl3 ipam** and register **vl3 network service** in the *floating domain* Note: *By default ipam prefix is `172.16.0.0/16` and client prefix len is `24`. We also have two vl3 nses in this example. So we expect to have two vl3 addresses: `172.16.0.0` and `172.16.1.0` that should be accessible by each client.* ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Start **nse-supplier-k8s** and client in the *cluster1*. ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Start **nse-supplier-k8s** and client in the *cluster2*. ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Wait for clients to be ready** @@ -74,15 +74,15 @@ kubectl --kubeconfig=$KUBECONFIG2 exec pods/alpine -n ns-floating-vl3-scale-from Cleanup floating domain: ```bash -kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` diff --git a/examples/interdomain/usecases/heal_floating-forwarder-death/README.md b/examples/interdomain/usecases/heal_floating-forwarder-death/README.md index e97856ec6917..30839ead635c 100644 --- a/examples/interdomain/usecases/heal_floating-forwarder-death/README.md +++ b/examples/interdomain/usecases/heal_floating-forwarder-death/README.md @@ -17,14 +17,14 @@ Make sure that you have completed steps from [heal](../../suites/heal) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -36,7 +36,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/heal_floating-nse-death/README.md b/examples/interdomain/usecases/heal_floating-nse-death/README.md index 1106fea54b74..1a4af08c08ca 100644 --- a/examples/interdomain/usecases/heal_floating-nse-death/README.md +++ b/examples/interdomain/usecases/heal_floating-nse-death/README.md @@ -18,14 +18,14 @@ Make sure that you have completed steps from [heal](../../suites/heal) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -37,7 +37,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/heal_floating-nsm-system-death/README.md b/examples/interdomain/usecases/heal_floating-nsm-system-death/README.md index 2eccf717b530..0873bc350295 100644 --- a/examples/interdomain/usecases/heal_floating-nsm-system-death/README.md +++ b/examples/interdomain/usecases/heal_floating-nsm-system-death/README.md @@ -18,14 +18,14 @@ Make sure that you have completed steps from [heal](../../suites/heal) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -37,7 +37,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -76,15 +76,15 @@ kubectl --kubeconfig=$KUBECONFIG3 delete ns nsm-system **6. Create new NSM components** ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **7. Wait until new NSM components are ready** diff --git a/examples/interdomain/usecases/heal_interdomain-nsmgr-death/README.md b/examples/interdomain/usecases/heal_interdomain-nsmgr-death/README.md index 3552e092c4b5..6c4692e4c925 100644 --- a/examples/interdomain/usecases/heal_interdomain-nsmgr-death/README.md +++ b/examples/interdomain/usecases/heal_interdomain-nsmgr-death/README.md @@ -19,7 +19,7 @@ Make sure that you have completed steps from [heal](../../suites/heal) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -31,7 +31,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/README.md b/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/README.md index 7164b1aa451e..39bfbcf8a6de 100644 --- a/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/README.md +++ b/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/README.md @@ -18,7 +18,7 @@ Make sure that you have completed steps from [heal](../../suites/heal) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -30,7 +30,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/heal_interdomain-registry-death/README.md b/examples/interdomain/usecases/heal_interdomain-registry-death/README.md index 2ee572095b73..f9875b7266cd 100644 --- a/examples/interdomain/usecases/heal_interdomain-registry-death/README.md +++ b/examples/interdomain/usecases/heal_interdomain-registry-death/README.md @@ -18,7 +18,7 @@ Make sure that you have completed steps from [heal](../../suites/heal) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -30,7 +30,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md index 2e88f9ae450d..5133707cebcd 100644 --- a/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md +++ b/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md @@ -15,7 +15,7 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -27,7 +27,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy client: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md index 5a668a2f4c3e..39e909399629 100644 --- a/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md +++ b/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md @@ -15,7 +15,7 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -27,7 +27,7 @@ kubectl --kubeconfig=$KUBECONFIG2 wait --for=condition=ready --timeout=1m pod -l Deploy NSC: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_dns/README.md b/examples/interdomain/usecases/interdomain_dns/README.md index 621082c7f9dd..f23c234ddaa6 100644 --- a/examples/interdomain/usecases/interdomain_dns/README.md +++ b/examples/interdomain/usecases/interdomain_dns/README.md @@ -13,14 +13,14 @@ Make sure that you have completed steps from [interdomain](../../suites/basic) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` **2. Deploy client on cluster1** Deploy client: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/nsm_consul/README.md b/examples/interdomain/usecases/nsm_consul/README.md index c55ba12f558d..bc7f75144f20 100644 --- a/examples/interdomain/usecases/nsm_consul/README.md +++ b/examples/interdomain/usecases/nsm_consul/README.md @@ -29,31 +29,31 @@ consul-k8s install -config-file=helm-consul-values.yaml -set global.image=hashic Deploy `counting` service and Consul workload on the second cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/server/counting.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/server/counting.yaml ``` Deploy networkservice on the second cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/netsvc.yaml ``` Start `auto-scale` networkservicemesh endpoints: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-client?ref=2937754b2d39bb47f94059b501c6555c8b146f03 -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-client?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Create kubernetes service for the networkservicemesh proxy-endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/service.yaml ``` Start `dashboard` networkservicemesh client on the first cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/client/dashboard.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/client/dashboard.yaml ``` Wait for the dashboard client to be ready @@ -80,7 +80,7 @@ kubectl --kubeconfig=$KUBECONFIG2 delete deploy counting Check UI and ensure that you see errors. Now lets start counting on cluster1: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml ``` Wait for new counting pod to be ready: ```bash @@ -101,13 +101,13 @@ kubectl --kubeconfig=$KUBECONFIG1 exec pod/dashboard-nsc -c cmd-nsc -- curl coun pkill -f "port-forward" ``` ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/client/dashboard.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-client?ref=2937754b2d39bb47f94059b501c6555c8b146f03 -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=2937754b2d39bb47f94059b501c6555c8b146f03 -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/client/dashboard.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-client?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_consul/netsvc.yaml kubectl --kubeconfig=$KUBECONFIG2 delete pods --all ``` ```bash diff --git a/examples/interdomain/usecases/nsm_consul_vl3/README.md b/examples/interdomain/usecases/nsm_consul_vl3/README.md index 49c4e262f0b3..1b7ee1681bbe 100644 --- a/examples/interdomain/usecases/nsm_consul_vl3/README.md +++ b/examples/interdomain/usecases/nsm_consul_vl3/README.md @@ -15,11 +15,11 @@ https://learn.hashicorp.com/tutorials/consul/service-mesh-with-envoy-proxy?in=co Start vl3, install Consul control plane and counting service on the first cluster and dashboard on the second: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for pods to be ready: @@ -548,9 +548,9 @@ pkill -f "port-forward" ``` ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` diff --git a/examples/interdomain/usecases/nsm_istio/README.md b/examples/interdomain/usecases/nsm_istio/README.md index b93dc8847d99..887ecfce9e44 100644 --- a/examples/interdomain/usecases/nsm_istio/README.md +++ b/examples/interdomain/usecases/nsm_istio/README.md @@ -24,24 +24,24 @@ istioctl --kubeconfig=$KUBECONFIG2 proxy-status Install networkservice for the second cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio/netsvc.yaml ``` Start `alpine` with networkservicemesh client on the first cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio/greeting/client.yaml ``` Start `auto-scale` networkservicemesh endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio/nse-auto-scale?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio/nse-auto-scale?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Install http-server for the second cluster: ```bash kubectl --kubeconfig=$KUBECONFIG2 label namespace default istio-injection=enabled -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio/greeting/server.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio/greeting/server.yaml ``` Wait for the `alpine` client to be ready: @@ -66,10 +66,10 @@ You have made a interdomain connection between two clusters via NSM + Istio! ## Cleanup ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio/greeting/server.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio/nse-auto-scale?ref=2937754b2d39bb47f94059b501c6555c8b146f03 -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio/greeting/client.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio/greeting/server.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio/nse-auto-scale?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio/netsvc.yaml kubectl --kubeconfig=$KUBECONFIG2 delete ns istio-system kubectl --kubeconfig=$KUBECONFIG2 label namespace default istio-injection- kubectl --kubeconfig=$KUBECONFIG2 delete pods --all diff --git a/examples/interdomain/usecases/nsm_istio_booking/README.md b/examples/interdomain/usecases/nsm_istio_booking/README.md index e81486ca285c..43f1e023b604 100644 --- a/examples/interdomain/usecases/nsm_istio_booking/README.md +++ b/examples/interdomain/usecases/nsm_istio_booking/README.md @@ -30,18 +30,18 @@ istioctl --kubeconfig=$KUBECONFIG2 proxy-status Install networkservice for the second cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio_booking/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio_booking/netsvc.yaml ``` Start `productpage` networkservicemesh client for the first cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml ``` Start `auto-scale` networkservicemesh endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio_booking/nse-auto-scale?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio_booking/nse-auto-scale?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Install istio booking example @@ -74,9 +74,9 @@ You have made a interdomain connection between two clusters via NSM + Istio! ```bash kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/istio/istio/release-1.13/samples/bookinfo/platform/kube/bookinfo.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio_booking/nse-auto-scale?ref=2937754b2d39bb47f94059b501c6555c8b146f03 -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_istio_booking/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio_booking/nse-auto-scale?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_istio_booking/netsvc.yaml kubectl --kubeconfig=$KUBECONFIG2 delete ns istio-system kubectl --kubeconfig=$KUBECONFIG2 label namespace default istio-injection- kubectl --kubeconfig=$KUBECONFIG2 delete pods --all diff --git a/examples/interdomain/usecases/nsm_kuma_universal_vl3/README.md b/examples/interdomain/usecases/nsm_kuma_universal_vl3/README.md index e2a537df375a..fc3f873eb655 100644 --- a/examples/interdomain/usecases/nsm_kuma_universal_vl3/README.md +++ b/examples/interdomain/usecases/nsm_kuma_universal_vl3/README.md @@ -7,7 +7,7 @@ Make sure that you have completed steps from [multiservicemesh](../../suites/mul ## Run 1. Start vl3 ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_kuma_universal_vl3/vl3-dns?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_kuma_universal_vl3/vl3-dns?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb kubectl --kubeconfig=$KUBECONFIG1 -n ns-dns-vl3 wait --for=condition=ready --timeout=5m pod -l app=vl3-ipam ``` @@ -27,7 +27,7 @@ kumactl generate tls-certificate --hostname=control-plane-kuma.my-vl3-network -- cp ./tls.crt ./ca.crt ``` ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_kuma_universal_vl3/namespace.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_kuma_universal_vl3/namespace.yaml kubectl --kubeconfig=$KUBECONFIG1 create secret generic general-tls-certs --namespace=kuma-system --from-file=./tls.key --from-file=./tls.crt --from-file=./ca.crt ``` ```bash @@ -43,7 +43,7 @@ resources: - control-plane.yaml patches: -- path: https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_kuma_universal_vl3/patch-control-plane.yaml +- path: https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_kuma_universal_vl3/patch-control-plane.yaml EOF ``` @@ -54,13 +54,13 @@ kubectl --kubeconfig=$KUBECONFIG1 apply -k . 5. Start redis database with the sidecar on the first cluster ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-redis.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-redis.yaml kubectl --kubeconfig=$KUBECONFIG1 -n kuma-demo wait --for=condition=ready --timeout=5m pod -l app=redis ``` 6. Start counter page with the sidecar on the second cluster ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-app.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-app.yaml kubectl --kubeconfig=$KUBECONFIG2 -n kuma-demo wait --for=condition=ready --timeout=5m pod -l app=demo-app ``` diff --git a/examples/ipsec_mechanism/README.md b/examples/ipsec_mechanism/README.md index 6b57e576714d..af9a85f1cc24 100644 --- a/examples/ipsec_mechanism/README.md +++ b/examples/ipsec_mechanism/README.md @@ -13,7 +13,7 @@ Unlike the [basic setup](../basic), which uses `Wireguard` as the default IP rem Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ipsec_mechanism?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ipsec_mechanism?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/k8s_monolith/external_nsc/README.md b/examples/k8s_monolith/external_nsc/README.md index 5e3a7f1d5a64..b6324f4ab17a 100644 --- a/examples/k8s_monolith/external_nsc/README.md +++ b/examples/k8s_monolith/external_nsc/README.md @@ -18,7 +18,7 @@ NSC requests the service and creates the required interface on the monolith: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for registry service exposing: diff --git a/examples/k8s_monolith/external_nsc/docker/README.md b/examples/k8s_monolith/external_nsc/docker/README.md index fe8a62cc0472..c531f96c1bb0 100644 --- a/examples/k8s_monolith/external_nsc/docker/README.md +++ b/examples/k8s_monolith/external_nsc/docker/README.md @@ -23,7 +23,7 @@ EOF Download docker-compose base file: ```bash -curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/apps/nsc-simple-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/apps/nsc-simple-docker/docker-compose.yaml -o docker-compose.yaml ``` Run docker-nsc: diff --git a/examples/k8s_monolith/external_nsc/spiffe_federation/README.md b/examples/k8s_monolith/external_nsc/spiffe_federation/README.md index b6ea94affb5e..fe3f31760e22 100644 --- a/examples/k8s_monolith/external_nsc/spiffe_federation/README.md +++ b/examples/k8s_monolith/external_nsc/spiffe_federation/README.md @@ -14,11 +14,11 @@ Once federation is bootstrapped, the trust bundle updates are fetched trough the Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` Get and store spire/spiffe bundles: diff --git a/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel/README.md b/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel/README.md index e7a332a5581b..41289e295d38 100644 --- a/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel/README.md +++ b/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel/README.md @@ -11,7 +11,7 @@ Make sure that you have completed steps from [external NSC](../../) Deploy NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/k8s_monolith/external_nse/README.md b/examples/k8s_monolith/external_nse/README.md index 22dc6ded6799..baeae20b31a7 100644 --- a/examples/k8s_monolith/external_nse/README.md +++ b/examples/k8s_monolith/external_nse/README.md @@ -18,7 +18,7 @@ This NSE creates the required interface on the monolith: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/k8s_monolith/external_nse/docker/README.md b/examples/k8s_monolith/external_nse/docker/README.md index 3c2499e7d541..8acdbdb90f83 100644 --- a/examples/k8s_monolith/external_nse/docker/README.md +++ b/examples/k8s_monolith/external_nse/docker/README.md @@ -24,7 +24,7 @@ EOF Download docker compose base file: ```bash -curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/apps/nse-simple-vl3-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/apps/nse-simple-vl3-docker/docker-compose.yaml -o docker-compose.yaml ``` Run docker-nse: diff --git a/examples/k8s_monolith/external_nse/spiffe_federation/README.md b/examples/k8s_monolith/external_nse/spiffe_federation/README.md index 43b478b92993..8ad725c2e553 100644 --- a/examples/k8s_monolith/external_nse/spiffe_federation/README.md +++ b/examples/k8s_monolith/external_nse/spiffe_federation/README.md @@ -14,11 +14,11 @@ Once federation is bootstrapped, the trust bundle updates are fetched trough the Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` Get and store spire/spiffe bundles: diff --git a/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel/README.md b/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel/README.md index 1e7fadad02bf..5564e836387d 100644 --- a/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel/README.md +++ b/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel/README.md @@ -11,7 +11,7 @@ Make sure that you have completed steps from [external NSE](../../) Deploy NSC: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Ethernet2Kernel/README.md b/examples/memory/Kernel2Ethernet2Kernel/README.md index 6156f519bad9..c975980496f6 100644 --- a/examples/memory/Kernel2Ethernet2Kernel/README.md +++ b/examples/memory/Kernel2Ethernet2Kernel/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [memory](../) setup. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Ethernet2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Ethernet2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Kernel/README.md b/examples/memory/Kernel2Kernel/README.md index 73e7f88e2373..7f4731441abd 100644 --- a/examples/memory/Kernel2Kernel/README.md +++ b/examples/memory/Kernel2Kernel/README.md @@ -19,7 +19,7 @@ Make sure that you have completed steps from [memory](../) setup. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/memory/Memif2Memif/README.md b/examples/memory/Memif2Memif/README.md index 7508246b0c4f..50da87f39a10 100644 --- a/examples/memory/Memif2Memif/README.md +++ b/examples/memory/Memif2Memif/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [memory](../) setup. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Memif2Memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Memif2Memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/memory/README.md b/examples/memory/README.md index fab63829fc89..676bed623094 100644 --- a/examples/memory/README.md +++ b/examples/memory/README.md @@ -11,7 +11,7 @@ Memory example contains setup and tear down logic with default NSM infrastructur Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder/README.md b/examples/multiforwarder/README.md index 75a3653761b3..50aa3914aadc 100644 --- a/examples/multiforwarder/README.md +++ b/examples/multiforwarder/README.md @@ -29,7 +29,7 @@ For the `worker` node: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder_vlantag/README.md b/examples/multiforwarder_vlantag/README.md index 55fe8e4873b5..9a43d956c7ac 100644 --- a/examples/multiforwarder_vlantag/README.md +++ b/examples/multiforwarder_vlantag/README.md @@ -30,7 +30,7 @@ For the `worker` node: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/observability/dashboard/README.md b/examples/observability/dashboard/README.md index 956b00dd9ac7..d04d315e700e 100644 --- a/examples/observability/dashboard/README.md +++ b/examples/observability/dashboard/README.md @@ -15,7 +15,7 @@ The dashboard consists of two parts: To run the dashboard in the cluster, execute the command: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/dashboard?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/dashboard?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for the dashboard pod to start: diff --git a/examples/observability/jaeger_and_prometheus/README.md b/examples/observability/jaeger_and_prometheus/README.md index 9187312492c9..abe2e7e43021 100644 --- a/examples/observability/jaeger_and_prometheus/README.md +++ b/examples/observability/jaeger_and_prometheus/README.md @@ -10,7 +10,7 @@ This example demonstrates how to setup Open Telemetry Collector with Jaeger and ## Run Apply Jaeger, Prometheus and OpenTelemetry Collector: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for OpenTelemetry Collector POD status ready: @@ -20,7 +20,7 @@ kubectl wait -n observability --timeout=1m --for=condition=ready pod -l app=open Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus/example?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus/example?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/observability/nsm_system/README.md b/examples/observability/nsm_system/README.md index fd1084964db6..8cedfb0322a6 100644 --- a/examples/observability/nsm_system/README.md +++ b/examples/observability/nsm_system/README.md @@ -12,7 +12,7 @@ Special env variable is used for this setup to support telemetry. Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/nsm_system?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/nsm_system?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/ovs/README.md b/examples/ovs/README.md index dcf303063419..aba5c2a02d9d 100644 --- a/examples/ovs/README.md +++ b/examples/ovs/README.md @@ -31,7 +31,7 @@ For the `worker` node: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ovs?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ovs?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/README.md b/examples/pss/README.md index 08e9edc27d5f..d6c1d0f15c6b 100644 --- a/examples/pss/README.md +++ b/examples/pss/README.md @@ -16,7 +16,7 @@ Based on the [PSS profile](https://kubernetes.io/docs/concepts/security/pod-secu Apply NSM resources: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/nsm-system?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/nsm-system?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/use-cases/nginx/README.md b/examples/pss/use-cases/nginx/README.md index c40a2187e044..2a0714590e6a 100644 --- a/examples/pss/use-cases/nginx/README.md +++ b/examples/pss/use-cases/nginx/README.md @@ -14,7 +14,7 @@ Make sure that you have completed steps from [PSS](../..). Deploy client and nginx-nse ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/use-cases/nginx?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/use-cases/nginx?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/remotevlan_ovs/README.md b/examples/remotevlan_ovs/README.md index 6b68f9ce496d..19b36fbecb39 100644 --- a/examples/remotevlan_ovs/README.md +++ b/examples/remotevlan_ovs/README.md @@ -44,7 +44,7 @@ Create ns for deployments: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_ovs?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_ovs?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for NSE application: diff --git a/examples/remotevlan_vpp/README.md b/examples/remotevlan_vpp/README.md index f0561362fa9a..780f224adeae 100644 --- a/examples/remotevlan_vpp/README.md +++ b/examples/remotevlan_vpp/README.md @@ -38,7 +38,7 @@ Create ns for deployments: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_vpp?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_vpp?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for NSE application: diff --git a/examples/spire/cluster1/README.md b/examples/spire/cluster1/README.md index 84af2015401d..4c44ec0af6ca 100644 --- a/examples/spire/cluster1/README.md +++ b/examples/spire/cluster1/README.md @@ -14,7 +14,7 @@ Check that we have config for the cluster: Apply spire deployments: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for PODs status ready: @@ -27,11 +27,11 @@ kubectl --kubeconfig=$KUBECONFIG1 wait -n spire --timeout=1m --for=condition=rea Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/cluster1/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/cluster1/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster2/README.md b/examples/spire/cluster2/README.md index e194198e26ca..6f4bcb0e0913 100644 --- a/examples/spire/cluster2/README.md +++ b/examples/spire/cluster2/README.md @@ -14,7 +14,7 @@ Check that we have config for the cluster: Apply spire deployments: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for PODs status ready: @@ -27,11 +27,11 @@ kubectl --kubeconfig=$KUBECONFIG2 wait -n spire --timeout=1m --for=condition=rea Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/cluster2/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/cluster2/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster3/README.md b/examples/spire/cluster3/README.md index 84766e3ba3cc..de141d9c7c16 100644 --- a/examples/spire/cluster3/README.md +++ b/examples/spire/cluster3/README.md @@ -14,7 +14,7 @@ Check that we have config for the cluster: Apply spire deployments: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for PODs status ready: @@ -27,11 +27,11 @@ kubectl --kubeconfig=$KUBECONFIG3 wait -n spire --timeout=1m --for=condition=rea Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/cluster3/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/cluster3/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/single_cluster/README.md b/examples/spire/single_cluster/README.md index ff640f211381..4439953a325e 100644 --- a/examples/spire/single_cluster/README.md +++ b/examples/spire/single_cluster/README.md @@ -6,7 +6,7 @@ This is a Spire setup for the single cluster scenario. To apply spire deployments following the next command: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for PODs status ready: @@ -19,11 +19,11 @@ kubectl wait -n spire --timeout=1m --for=condition=ready pod -l app=spire-agent Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/single_cluster_csi/README.md b/examples/spire/single_cluster_csi/README.md index bec9bc652b7b..dc774089161a 100644 --- a/examples/spire/single_cluster_csi/README.md +++ b/examples/spire/single_cluster_csi/README.md @@ -6,7 +6,7 @@ This setup deploys SPIRE along with [SPIFFE CSI driver](https://github.com/spiff To apply spire deployments following the next command: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster_csi?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster_csi?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for PODs status ready: @@ -19,11 +19,11 @@ kubectl wait -n spire --timeout=1m --for=condition=ready pod -l app=spire-agent Apply the ClusterSPIFFEID CR for the cluster: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/sriov/README.md b/examples/sriov/README.md index 2d8e3a090bcc..fa883a5056c8 100644 --- a/examples/sriov/README.md +++ b/examples/sriov/README.md @@ -28,7 +28,7 @@ For the `worker` node: Apply NSM resources for sriov tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ## Includes diff --git a/examples/sriov_vlantag/README.md b/examples/sriov_vlantag/README.md index 7c5e605ce87b..9d955ec56176 100644 --- a/examples/sriov_vlantag/README.md +++ b/examples/sriov_vlantag/README.md @@ -28,7 +28,7 @@ For the `worker` node: Apply NSM resources for sriov tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` ## Includes diff --git a/examples/use-cases/Kernel2Ethernet2Kernel/README.md b/examples/use-cases/Kernel2Ethernet2Kernel/README.md index 1218ed4fda65..b7d91d0ba641 100644 --- a/examples/use-cases/Kernel2Ethernet2Kernel/README.md +++ b/examples/use-cases/Kernel2Ethernet2Kernel/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md index 4ad9a7be4cb7..2be5b9de7dd5 100644 --- a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md +++ b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md @@ -6,7 +6,7 @@ This example shows that remote kernel over Ethernet connection and VFIO connecti Deploy NSCs and NSEs: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md index d39e01dc74f2..1d03048e56e6 100644 --- a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md +++ b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md @@ -8,7 +8,7 @@ This example shows that remote kernel over Ethernet connection and VFIO connecti Deploy NSCs and NSEs: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Memif/README.md b/examples/use-cases/Kernel2Ethernet2Memif/README.md index 657a2bae0114..efeefb8cbea0 100644 --- a/examples/use-cases/Kernel2Ethernet2Memif/README.md +++ b/examples/use-cases/Kernel2Ethernet2Memif/README.md @@ -14,7 +14,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Kernel/README.md b/examples/use-cases/Kernel2IP2Kernel/README.md index 4d49f9aec4e4..a60fa7ae6a05 100644 --- a/examples/use-cases/Kernel2IP2Kernel/README.md +++ b/examples/use-cases/Kernel2IP2Kernel/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Memif/README.md b/examples/use-cases/Kernel2IP2Memif/README.md index 523d961e9f01..786247368921 100644 --- a/examples/use-cases/Kernel2IP2Memif/README.md +++ b/examples/use-cases/Kernel2IP2Memif/README.md @@ -14,7 +14,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel/README.md b/examples/use-cases/Kernel2Kernel/README.md index c65688f90ca3..ec3297c749d4 100644 --- a/examples/use-cases/Kernel2Kernel/README.md +++ b/examples/use-cases/Kernel2Kernel/README.md @@ -19,7 +19,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2KernelVLAN/README.md b/examples/use-cases/Kernel2KernelVLAN/README.md index b935e135f6a5..3979ef298d07 100644 --- a/examples/use-cases/Kernel2KernelVLAN/README.md +++ b/examples/use-cases/Kernel2KernelVLAN/README.md @@ -16,7 +16,7 @@ hugepage, so in this case NSE pod should be created with memory limit > 2.2 GB. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2KernelVLAN?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2KernelVLAN?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md index 730743bff23a..d12a675e2933 100644 --- a/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md +++ b/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md @@ -6,7 +6,7 @@ This example shows that local kernel connection and VFIO connection can be setup Deploy NSCs and NSEs: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2Noop?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2Noop?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md index 61cd428c761c..baa30e5a9ab4 100644 --- a/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md +++ b/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md @@ -9,7 +9,7 @@ SR-IOV VF uses VLAN tag. Deploy NSCs and NSEs: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Memif/README.md b/examples/use-cases/Kernel2Memif/README.md index 5fb1b57a544e..264e2b0aaf86 100644 --- a/examples/use-cases/Kernel2Memif/README.md +++ b/examples/use-cases/Kernel2Memif/README.md @@ -14,7 +14,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanBreakout/README.md b/examples/use-cases/Kernel2RVlanBreakout/README.md index 951e8fe30656..131dcd3f10f8 100644 --- a/examples/use-cases/Kernel2RVlanBreakout/README.md +++ b/examples/use-cases/Kernel2RVlanBreakout/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [remotevlan_ovs](../../remotevlan_o Deploy iperf server: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanBreakout?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanBreakout?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanInternal/README.md b/examples/use-cases/Kernel2RVlanInternal/README.md index 967c5afc379a..171139b7f080 100644 --- a/examples/use-cases/Kernel2RVlanInternal/README.md +++ b/examples/use-cases/Kernel2RVlanInternal/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [remotevlan_ovs](../../remotevlan_o Deploy iperf server: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanInternal?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanInternal?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanMultiNS/README.md b/examples/use-cases/Kernel2RVlanMultiNS/README.md index 7284982f5e2c..8dac0b4e6ced 100644 --- a/examples/use-cases/Kernel2RVlanMultiNS/README.md +++ b/examples/use-cases/Kernel2RVlanMultiNS/README.md @@ -12,19 +12,19 @@ Make sure that you have completed steps from [remotevlan_ovs](../../remotevlan_o Deployment in first namespace: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-1?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Deployment in second namespace: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Deployment in third namespace: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Kernel/README.md b/examples/use-cases/Memif2Ethernet2Kernel/README.md index 7276fb0a52ac..aaca4ceca623 100644 --- a/examples/use-cases/Memif2Ethernet2Kernel/README.md +++ b/examples/use-cases/Memif2Ethernet2Kernel/README.md @@ -15,7 +15,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Memif/README.md b/examples/use-cases/Memif2Ethernet2Memif/README.md index 2f94ba7f2305..bca39cc3f9b7 100644 --- a/examples/use-cases/Memif2Ethernet2Memif/README.md +++ b/examples/use-cases/Memif2Ethernet2Memif/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Kernel/README.md b/examples/use-cases/Memif2IP2Kernel/README.md index 5093c24703df..e0f6728af81f 100644 --- a/examples/use-cases/Memif2IP2Kernel/README.md +++ b/examples/use-cases/Memif2IP2Kernel/README.md @@ -15,7 +15,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Memif/README.md b/examples/use-cases/Memif2IP2Memif/README.md index 9ba81720f63c..632c97455a8f 100644 --- a/examples/use-cases/Memif2IP2Memif/README.md +++ b/examples/use-cases/Memif2IP2Memif/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Kernel/README.md b/examples/use-cases/Memif2Kernel/README.md index 67c047baad53..57ea1a3cbef0 100644 --- a/examples/use-cases/Memif2Kernel/README.md +++ b/examples/use-cases/Memif2Kernel/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Kernel?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Kernel?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Memif/README.md b/examples/use-cases/Memif2Memif/README.md index 7bb49e1fc8e2..befc6fa33637 100644 --- a/examples/use-cases/Memif2Memif/README.md +++ b/examples/use-cases/Memif2Memif/README.md @@ -13,7 +13,7 @@ Make sure that you have completed steps from [basic](../../basic) or [memory](.. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Memif?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Memif?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/SmartVF2SmartVF/README.md b/examples/use-cases/SmartVF2SmartVF/README.md index e3baca496d7e..bbabf4143e8b 100644 --- a/examples/use-cases/SmartVF2SmartVF/README.md +++ b/examples/use-cases/SmartVF2SmartVF/README.md @@ -10,7 +10,7 @@ Make sure that you have completed steps from [ovs](../../ovs) setup. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SmartVF2SmartVF?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SmartVF2SmartVF?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2Noop/README.md b/examples/use-cases/SriovKernel2Noop/README.md index e9d2bd7defff..718d65e80d2a 100644 --- a/examples/use-cases/SriovKernel2Noop/README.md +++ b/examples/use-cases/SriovKernel2Noop/README.md @@ -10,7 +10,7 @@ Make sure that you have completed steps from [sriov](../../sriov) setup. Deploy ponger: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -25,7 +25,7 @@ kubectl -n ns-sriov-kernel2noop exec deploy/ponger -- ip a | grep "172.16.1.100" Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2NoopVlanTag/README.md b/examples/use-cases/SriovKernel2NoopVlanTag/README.md index b9cb23b59610..dfe10d2ff866 100644 --- a/examples/use-cases/SriovKernel2NoopVlanTag/README.md +++ b/examples/use-cases/SriovKernel2NoopVlanTag/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [sriov](../../sriov_vlantag) setup. Deploy ponger: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag/ponger?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag/ponger?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: @@ -27,7 +27,7 @@ kubectl -n ns-sriov-kernel2noop-vlantag exec deploy/ponger -- ip a | grep "172.1 Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2Noop/README.md b/examples/use-cases/Vfio2Noop/README.md index aa85631e65b7..f9c1e633a893 100644 --- a/examples/use-cases/Vfio2Noop/README.md +++ b/examples/use-cases/Vfio2Noop/README.md @@ -10,7 +10,7 @@ Make sure that you have completed steps from [sriov](../../sriov) setup. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2Noop?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2Noop?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2NoopVlanTag/README.md b/examples/use-cases/Vfio2NoopVlanTag/README.md index c842cac489fd..58c6bede0859 100644 --- a/examples/use-cases/Vfio2NoopVlanTag/README.md +++ b/examples/use-cases/Vfio2NoopVlanTag/README.md @@ -12,7 +12,7 @@ Make sure that you have completed steps from [sriov](../../sriov_vlantag) setup. Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2NoopVlanTag?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2NoopVlanTag?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for applications ready: diff --git a/examples/use-cases/vl3-basic/README.md b/examples/use-cases/vl3-basic/README.md index 8c166c415622..515dcb34e980 100644 --- a/examples/use-cases/vl3-basic/README.md +++ b/examples/use-cases/vl3-basic/README.md @@ -13,7 +13,7 @@ Diagram: Deploy network service, nsc and vl3 nses (See at `kustomization.yaml`): ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/vl3-basic?ref=2937754b2d39bb47f94059b501c6555c8b146f03 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/vl3-basic?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb ``` Wait for clients to be ready: diff --git a/to-ref.sh b/to-ref.sh index 95f9d4d0a8df..61aadb127c9e 100755 --- a/to-ref.sh +++ b/to-ref.sh @@ -17,13 +17,13 @@ get_root() { escape "${root}" } -FILE_PATTERN="$(escape 'https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/2937754b2d39bb47f94059b501c6555c8b146f03/\1')" +FILE_PATTERN="$(escape 'https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e436f2af1de4b7a5687ea5469199c44a4268a5cb/\1')" grep "$(pwd)" -rl examples/* | while IFS= read -r file; do root="$(get_root "$file")" sedi -E "s/${root//./\.}\/([^ ]*\.[a-z]+)/${FILE_PATTERN}/g" "${file}" done -DIR_PATTERN="$(escape 'https://github.com/networkservicemesh/deployments-k8s/\1?ref=2937754b2d39bb47f94059b501c6555c8b146f03')" +DIR_PATTERN="$(escape 'https://github.com/networkservicemesh/deployments-k8s/\1?ref=e436f2af1de4b7a5687ea5469199c44a4268a5cb')" grep "$(pwd)" -rl examples/* | while IFS= read -r file; do root="$(get_root "$file")" sedi -E "s/${root//./\.}\/([^ ]*)/${DIR_PATTERN}/g" "${file}"