From 3510c53e5fef5579077a2aecfd8c6201e4664f99 Mon Sep 17 00:00:00 2001 From: nsmbot Date: Tue, 20 Aug 2024 09:13:29 +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 a94ca997baff..8efa61592513 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/afxdp?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/basic/README.md b/examples/basic/README.md index ca4902d94764..f7171675b996 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/features/annotated-namespace/README.md b/examples/features/annotated-namespace/README.md index 8aac9cb0f2fb..e4ebf5a5d565 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/annotated-namespace?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/features/annotated-namespace/client.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 328bd0329cf4..c67b5ad6a349 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/change-nse-dynamically?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/features/change-nse-dynamically/green-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 ff867853b30f..f0057ad8a9fc 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dns?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 fd3ebe0644e0..df4217fae43e 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 3bd32c931f97..77569d5814a9 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2Kernel_dual_stack?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 eb690a4454a3..8acd756bf795 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 43081bf8478f..713ae9d5ff1d 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes-client?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/exclude-prefixes/README.md b/examples/features/exclude-prefixes/README.md index e42c7f37ce44..3dc9f02dd9d5 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes/configmap?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md index 0706e36a8148..b1f723c12d71 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Kernel_ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md index 2b1e6caa9f15..f566258708d7 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Memif_ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2Kernel_ipv6/README.md index af46880a26fa..7142eb516bed 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2Kernel_ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md index 663f5b6c2cea..d54ea3204fc2 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Kernel_ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md b/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md index f96ccdf660a2..17eaaca0c5a4 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Memif_ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2Memif_ipv6/README.md b/examples/features/ipv6/Memif2Memif_ipv6/README.md index d278da468a2d..aab2948f78e6 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2Memif_ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/jaeger/README.md b/examples/features/jaeger/README.md index 69bec58bbd64..a4f6000e16b0 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/jaeger?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/opentelemetry?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Apply Spire deployments (required for NSM system) ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/nsm-system?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/features/multiple-services/README.md b/examples/features/multiple-services/README.md index 0cf73c6618ff..5813b705e63e 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/multiple-services?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/mutually-aware-nses/README.md b/examples/features/mutually-aware-nses/README.md index d350b55ba1f7..09aed24688bd 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/mutually-aware-nses?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/nse-composition/README.md b/examples/features/nse-composition/README.md index 4e760c54fd5f..e33c00f3da76 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/nse-composition?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/opa/README.md b/examples/features/opa/README.md index ecbcbd97ce59..b950dc2657ec 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/opa?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/policy-based-routing/README.md b/examples/features/policy-based-routing/README.md index 3eed13db1314..174ab6cb9b48 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/policy-based-routing?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/scale-from-zero/README.md b/examples/features/scale-from-zero/README.md index 511855b665ea..c91cbc253d15 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scale-from-zero?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/scaled-registry/README.md b/examples/features/scaled-registry/README.md index 26ae2d6566ae..6a5cae136d32 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scaled-registry?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for NSE to be ready: diff --git a/examples/features/select-forwarder/README.md b/examples/features/select-forwarder/README.md index e59e40be980f..7970eb993e1d 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/select-forwarder?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/vl3-dns/README.md b/examples/features/vl3-dns/README.md index 7f6b6f5a32ee..a5d03766b81d 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-dns?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for clients to be ready: diff --git a/examples/features/vl3-ipv6/README.md b/examples/features/vl3-ipv6/README.md index 32a5d916dd27..639aef6c1bce 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-ipv6?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for clients to be ready: diff --git a/examples/features/vl3-lb/README.md b/examples/features/vl3-lb/README.md index 759509831618..c58d4b538957 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-lb?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 aff1f829d126..7330eedf66a8 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-scale-from-zero?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/webhook-smartvf/README.md b/examples/features/webhook-smartvf/README.md index efb7af21da3a..c6183646d603 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook-smartvf?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/features/webhook/README.md b/examples/features/webhook/README.md index 7502d675ec42..d5d0d1a570cd 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/dataplane-interrupt/README.md b/examples/heal/dataplane-interrupt/README.md index 0598c23dbbed..524b15efa685 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/dataplane-interrupt?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/local-forwarder-death/README.md b/examples/heal/local-forwarder-death/README.md index 462ed91c13c5..94a7aed78e17 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 0e5882b841e9..20b8a68d7b07 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-remote-forwarder?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/local-nse-death/README.md b/examples/heal/local-nse-death/README.md index 63414703597f..b0aac65192f5 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-before-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-after-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Restore NSE pod: diff --git a/examples/heal/local-nsm-system-restart/README.md b/examples/heal/local-nsm-system-restart/README.md index cbb26aa90df8..fb93ebbe460e 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsm-system-restart?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 314ca3e21a74..45824d6f9d60 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-forwarder-memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 eced4f6c23ea..fb2490eab7ce 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-before-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-after-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 6b4eef725440..5125bc0ea0f6 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-remote-nsmgr?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/local-nsmgr-restart/README.md b/examples/heal/local-nsmgr-restart/README.md index 1f2e31cc7e8d..cf3419c4570e 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-restart?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/registry-local-endpoint/README.md b/examples/heal/registry-local-endpoint/README.md index 7144b18be3e9..7c7b9f1a2c79 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-first?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-second?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Waiting for new ones: diff --git a/examples/heal/registry-remote-forwarder/README.md b/examples/heal/registry-remote-forwarder/README.md index 288febb9e71f..404f236b03ca 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-forwarder?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/registry-remote-nsmgr/README.md b/examples/heal/registry-remote-nsmgr/README.md index db76f5aaaa75..118bd685eea2 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-nsmgr?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/registry-restart/README.md b/examples/heal/registry-restart/README.md index e2033bb9a3d1..249b4732317d 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-before-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-after-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 f34f8d577c94..06ecd4fa9232 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death-ip?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/remote-forwarder-death/README.md b/examples/heal/remote-forwarder-death/README.md index e1b7f220cc35..f5651e808d3c 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 7f41a7f1c71d..075837127b53 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-before-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-after-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 081e1616ba1f..febd239db9a3 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-before-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-after-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 67bb949f1db6..a53a3b995a86 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsm-system-restart-memif-ip?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Ping from NSC to NSE: diff --git a/examples/heal/remote-nsmgr-death/README.md b/examples/heal/remote-nsmgr-death/README.md index c8014b93fa66..434045f63a8e 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/remote-nse?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/nsmgr-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/local-nse?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea -n nsm-system +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/nsmgr?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a -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 600baf65e197..4c6c0e64a40b 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-before-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-after-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 0e962e49279f..13bd8b7855a9 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart-ip?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/remote-nsmgr-restart/README.md b/examples/heal/remote-nsmgr-restart/README.md index 4b0ae60faee7..2115b6080f15 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/spire-agent-restart/README.md b/examples/heal/spire-agent-restart/README.md index 97be01dc632a..a88e36c3cc89 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-agent-restart?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 38a3d75d73da..1862642a8926 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-agent-restart?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/spire-server-restart/README.md b/examples/heal/spire-server-restart/README.md index c28f4909b019..525081d914fc 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-restart?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/heal/spire-upgrade/README.md b/examples/heal/spire-upgrade/README.md index b0c77b4fd28c..597d3131a9b4 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-upgrade?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 9dc832311021..11280dccc470 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nscs-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 d15d632ae916..2fe1252f4887 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nse-death?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 a9e7e7f12658..4f7f97b69fed 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal_extended/component-restart?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 bfd340f6376d..e57db7c1f2c0 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 50a31f75b158..94becf9f0738 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 4a5efc144d69..f93694cda307 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 84e1f4e65b32..d68baf19d861 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster1-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster2-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 08fc77f43559..28b8997bae06 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md index e05c34f1871c..9e9e1797593d 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md index c258de22569c..56fbaf41e93d 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md index 88a467f8565d..69e2ece52bbc 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md index fb38bf7c0b8b..7f594d2417f9 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md index 94dfc195f9c7..41afb48a5b4f 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md index 4f7b04ce8395..f4bd091ec419 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md b/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md index 8eff3155ffb5..afc31f0da2eb 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_dns/README.md b/examples/interdomain/usecases/floating_dns/README.md index 49673e57ec1c..b4578a981d79 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 8d42fc6c2bd2..6f5ec2d7338f 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 2e64fddb75e8..f9f90116149a 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` diff --git a/examples/interdomain/usecases/floating_vl3-dns/README.md b/examples/interdomain/usecases/floating_vl3-dns/README.md index b2c24f1df6ed..bd9ce95baa9e 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 2. Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 3. Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 562469c30768..7c6c6a0ec65a 100644 --- a/examples/interdomain/usecases/floating_vl3-scale-from-zero/README.md +++ b/examples/interdomain/usecases/floating_vl3-scale-from-zero/README.md @@ -18,17 +18,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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **2. Wait for clients to be ready** @@ -72,15 +72,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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` diff --git a/examples/interdomain/usecases/heal_floating-forwarder-death/README.md b/examples/interdomain/usecases/heal_floating-forwarder-death/README.md index f14556c7cb96..e73adfdbbb95 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 116f827d6f8b..0e163745d5db 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 445da997be2f..1b71cc831b35 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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 6236853eb90a..8d77ebda2972 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 aadfc6ef28d3..b8aa08ff8f17 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 7a46a1ed4751..ece483b5f10b 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md index c28995bfc098..cfeb1957e5ca 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md index 310c9905162e..0eaf73eb8e2a 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_dns/README.md b/examples/interdomain/usecases/interdomain_dns/README.md index 34fbf1124cef..9b40a1ec3b92 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` **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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/nsm_consul/README.md b/examples/interdomain/usecases/nsm_consul/README.md index e6c3b814d945..9acec6e156f9 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/server/counting.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-client?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Create kubernetes service for the networkservicemesh proxy-endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/client/dashboard.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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=edb2629acbb56ad68a31489621b8aa25a1ac160a +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 ddb2df483798..c3849c40e835 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` diff --git a/examples/interdomain/usecases/nsm_istio/README.md b/examples/interdomain/usecases/nsm_istio/README.md index c309ef7f859f..ff1f548684e2 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio/nse-auto-scale?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio/greeting/server.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio/greeting/client.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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=edb2629acbb56ad68a31489621b8aa25a1ac160a +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 f0a8a6103603..443e9870579f 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio_booking/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio_booking/nse-auto-scale?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/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=edb2629acbb56ad68a31489621b8aa25a1ac160a +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 cddfd12e186f..6348ce395c4a 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_kuma_universal_vl3/vl3-dns?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_kuma_universal_vl3/namespace.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_kuma_universal_vl3/patch-control-plane.yaml +- path: https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-redis.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-app.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 cb323df4ff05..0a58bc60f9c3 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ipsec_mechanism?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/k8s_monolith/external_nsc/README.md b/examples/k8s_monolith/external_nsc/README.md index 870cb52c703e..53e03db7f1b5 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 4a89fba1dd77..f679fd72f006 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/apps/nsc-simple-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 f7d3299ec25b..d938d059ee0c 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 d8de90ed74bd..7ced20bfd7c4 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/k8s_monolith/external_nse/README.md b/examples/k8s_monolith/external_nse/README.md index 3c6f672df802..cd632dfa7739 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 b64c3fec7e5e..1584a7922404 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/apps/nse-simple-vl3-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 e57f8613c1ca..df1fc7bddaaf 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 d8ec106ec73e..742ac135a0b9 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Ethernet2Kernel/README.md b/examples/memory/Kernel2Ethernet2Kernel/README.md index b3df80b3d415..301fb4b92dca 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Ethernet2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Kernel/README.md b/examples/memory/Kernel2Kernel/README.md index f72ab33d1d52..62ade3412983 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/memory/Memif2Memif/README.md b/examples/memory/Memif2Memif/README.md index fed1e2e989f3..acc99fb4990c 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Memif2Memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/memory/README.md b/examples/memory/README.md index 85aa54de6868..563584657dff 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder/README.md b/examples/multiforwarder/README.md index 266021980e0b..de94a7467e6a 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder_vlantag/README.md b/examples/multiforwarder_vlantag/README.md index 6d13f1470818..32dc85bb1cc4 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/observability/dashboard/README.md b/examples/observability/dashboard/README.md index eff62670aaea..6be320c79f3a 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/dashboard?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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 d5ef9431ef90..64c55bb3bf1c 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus/example?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/observability/nsm_system/README.md b/examples/observability/nsm_system/README.md index e8c13eb6ab29..55d1b2fa0b75 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/nsm_system?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/ovs/README.md b/examples/ovs/README.md index e4a982de5ad2..7155cff0fc55 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ovs?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/README.md b/examples/pss/README.md index 3f8f6d6c166e..7705268dc65b 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/nsm-system?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/use-cases/nginx/README.md b/examples/pss/use-cases/nginx/README.md index 3742a5105669..3d17a8191b23 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/use-cases/nginx?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/remotevlan_ovs/README.md b/examples/remotevlan_ovs/README.md index bc530ad009a5..c3aab581ca82 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_ovs?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for NSE application: diff --git a/examples/remotevlan_vpp/README.md b/examples/remotevlan_vpp/README.md index 706b5a4c4e24..9bf95eaf4c6d 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_vpp?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for NSE application: diff --git a/examples/spire/cluster1/README.md b/examples/spire/cluster1/README.md index 4d697c70a46c..e30c7a9f7a25 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/cluster1/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/cluster1/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster2/README.md b/examples/spire/cluster2/README.md index 5ae654f5e636..44768f9a82bb 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/cluster2/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/cluster2/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster3/README.md b/examples/spire/cluster3/README.md index facb6fbd74cc..7e80660cc264 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/cluster3/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/cluster3/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 2d1fefa88bd4..60fe421e41f4 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/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 0298a1d5b6bc..e6e44232bc59 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster_csi?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/sriov/README.md b/examples/sriov/README.md index e3542d06a178..ca44a7a1a009 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ## Includes diff --git a/examples/sriov_vlantag/README.md b/examples/sriov_vlantag/README.md index a9e2e6734cae..4125dc755e90 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` ## Includes diff --git a/examples/use-cases/Kernel2Ethernet2Kernel/README.md b/examples/use-cases/Kernel2Ethernet2Kernel/README.md index 5fdd4346f125..79e03b0dd98a 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md index 4f989c3425c0..35ce3ab6a073 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md index 715684b4f3d3..e13c861b3e27 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Memif/README.md b/examples/use-cases/Kernel2Ethernet2Memif/README.md index 5ff27181e6ce..98637c1360f0 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Kernel/README.md b/examples/use-cases/Kernel2IP2Kernel/README.md index 325e2f9ddea9..5dafc706dd29 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Memif/README.md b/examples/use-cases/Kernel2IP2Memif/README.md index 0c4bf4ad7183..40cd90605dc6 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel/README.md b/examples/use-cases/Kernel2Kernel/README.md index b67159c64e61..91c7667c9291 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2KernelVLAN/README.md b/examples/use-cases/Kernel2KernelVLAN/README.md index 68104f68d09b..ecdbbd44e68f 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2KernelVLAN?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md index f7888cbf4c9f..5550721309a3 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2Noop?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md index 850393e95b4d..66a24ab792a9 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Memif/README.md b/examples/use-cases/Kernel2Memif/README.md index f4d99f39e87f..94b30668737b 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanBreakout/README.md b/examples/use-cases/Kernel2RVlanBreakout/README.md index 3947feb1ad7e..5570bb2e3955 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanBreakout?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanInternal/README.md b/examples/use-cases/Kernel2RVlanInternal/README.md index 0c1879a4df8c..3ca858b39e61 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanInternal?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanMultiNS/README.md b/examples/use-cases/Kernel2RVlanMultiNS/README.md index 7bf2be099a67..bc4f2c5c0068 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Deployment in second namespace: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Deployment in third namespace: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Kernel/README.md b/examples/use-cases/Memif2Ethernet2Kernel/README.md index 6cfa88bc343e..ba724af40279 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Memif/README.md b/examples/use-cases/Memif2Ethernet2Memif/README.md index c2394f0fedfb..6200efce9372 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Kernel/README.md b/examples/use-cases/Memif2IP2Kernel/README.md index 039afb9019c1..f895c1500880 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Memif/README.md b/examples/use-cases/Memif2IP2Memif/README.md index 41e4b05612e4..75f66c37d1f1 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Kernel/README.md b/examples/use-cases/Memif2Kernel/README.md index ebdf5cd916f5..f34e913955e8 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Kernel?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Memif/README.md b/examples/use-cases/Memif2Memif/README.md index 4d976fc6c4bf..bc4742f62946 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Memif?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/SmartVF2SmartVF/README.md b/examples/use-cases/SmartVF2SmartVF/README.md index 344264323587..896a8a8222ef 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SmartVF2SmartVF?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2Noop/README.md b/examples/use-cases/SriovKernel2Noop/README.md index bb31217034d9..53872f2eb9f5 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2NoopVlanTag/README.md b/examples/use-cases/SriovKernel2NoopVlanTag/README.md index 2c9957f65762..579ad32ef4c8 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag/ponger?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2Noop/README.md b/examples/use-cases/Vfio2Noop/README.md index ff5414d34ae9..21ef547f3d2a 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2Noop?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2NoopVlanTag/README.md b/examples/use-cases/Vfio2NoopVlanTag/README.md index 180097b0229b..0ee27907a3bc 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2NoopVlanTag?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for applications ready: diff --git a/examples/use-cases/vl3-basic/README.md b/examples/use-cases/vl3-basic/README.md index e48a8adb3fe9..d897910b0b9b 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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/vl3-basic?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a ``` Wait for clients to be ready: diff --git a/to-ref.sh b/to-ref.sh index 23ecb6970526..54740676fea3 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/6b7106ea0d9e853e9827c469b45c6805a97cf4ea/\1')" +FILE_PATTERN="$(escape 'https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/edb2629acbb56ad68a31489621b8aa25a1ac160a/\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=6b7106ea0d9e853e9827c469b45c6805a97cf4ea')" +DIR_PATTERN="$(escape 'https://github.com/networkservicemesh/deployments-k8s/\1?ref=edb2629acbb56ad68a31489621b8aa25a1ac160a')" grep "$(pwd)" -rl examples/* | while IFS= read -r file; do root="$(get_root "$file")" sedi -E "s/${root//./\.}\/([^ ]*)/${DIR_PATTERN}/g" "${file}"