From 5afb9268d4528e3227b5184ed9984742c959ba2b Mon Sep 17 00:00:00 2001 From: nsmbot Date: Thu, 17 Oct 2024 23:55:03 +0000 Subject: [PATCH] Update references Signed-off-by: nsmbot --- examples/afxdp/README.md | 2 +- examples/basic/README.md | 2 +- .../features/annotated-namespace/README.md | 4 +-- .../features/change-nse-dynamically/README.md | 8 ++--- examples/features/dns/README.md | 2 +- .../Kernel2IP2Kernel_dual_stack/README.md | 2 +- .../Kernel2Kernel_dual_stack/README.md | 2 +- .../dual-stack/vl3-dual-stack/README.md | 4 +-- .../exclude-prefixes-client/README.md | 2 +- examples/features/exclude-prefixes/README.md | 4 +-- examples/features/ipam-policies/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 +-- 149 files changed, 283 insertions(+), 283 deletions(-) diff --git a/examples/afxdp/README.md b/examples/afxdp/README.md index eefd3a0f4c70..169391c5e8aa 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/afxdp?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/basic/README.md b/examples/basic/README.md index d8eeeab4560c..72db97b553a0 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/features/annotated-namespace/README.md b/examples/features/annotated-namespace/README.md index c16410cff946..bdc0712aa392 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/annotated-namespace?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/features/annotated-namespace/client.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 2076bd37eec5..2405514d51ae 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/change-nse-dynamically?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/features/change-nse-dynamically/green-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 8b1e4078d291..ecb0136fc9b8 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dns?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 98ffe7c2ca5a..9da770a98251 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 57bfc3a5a16b..b29803ff0f1b 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2Kernel_dual_stack?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 56de9624f788..a99ab2d3dd40 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack?ref=37a7407b8fbfe6620c868366006c3e722d33f38e +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 fc445ca91efe..6481a124409c 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes-client?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/exclude-prefixes/README.md b/examples/features/exclude-prefixes/README.md index f4c984a43c3d..f00c13354730 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes/configmap?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/ipam-policies/README.md b/examples/features/ipam-policies/README.md index 4f5359a6ae30..d24e8e631d67 100644 --- a/examples/features/ipam-policies/README.md +++ b/examples/features/ipam-policies/README.md @@ -17,7 +17,7 @@ Make sure that you have completed steps from [basic](../../basic) setup. Deploy the client and the first NSE with CIDR `172.16.1.0/31` and `default` IPAM Policy: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipam-policies?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipam-policies?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: @@ -45,7 +45,7 @@ kubectl delete pod -l app=first-nse -n ns-ipam-policies Apply the second NSE with CIDR `172.16.2.0/31` and `strict` IPAM Policy: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/features/ipam-policies/second-nse.yaml -n ns-ipam-policies +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/features/ipam-policies/second-nse.yaml -n ns-ipam-policies ``` Ping the second NSE from the client: diff --git a/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md index ecdc2b0074b9..51499ab85ac5 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Kernel_ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md index 8db06ff3b39c..a60e44a18dc0 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Memif_ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2Kernel_ipv6/README.md index 37ab433411b8..6066546b66c2 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2Kernel_ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md index f021c156cc72..16bc2cd4dc72 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Kernel_ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md b/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md index c0b3717cac13..8890cc9ee499 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Memif_ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2Memif_ipv6/README.md b/examples/features/ipv6/Memif2Memif_ipv6/README.md index fe953005d982..e2e3627bf19f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2Memif_ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/jaeger/README.md b/examples/features/jaeger/README.md index 756ea15adeb3..640c1f16f9ff 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/jaeger?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/opentelemetry?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Apply Spire deployments (required for NSM system) ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/nsm-system?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/features/multiple-services/README.md b/examples/features/multiple-services/README.md index 11082ba9cfa5..35d13721e185 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/multiple-services?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/mutually-aware-nses/README.md b/examples/features/mutually-aware-nses/README.md index 8c10ad705828..51589c94c3e2 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/mutually-aware-nses?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/nse-composition/README.md b/examples/features/nse-composition/README.md index 408f8a4013a5..8a50731e6089 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/nse-composition?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/opa/README.md b/examples/features/opa/README.md index 2245cb7d4399..a4b13c4f4132 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/opa?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/policy-based-routing/README.md b/examples/features/policy-based-routing/README.md index a46eb7f2fbf0..c586c2929b2a 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/policy-based-routing?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/scale-from-zero/README.md b/examples/features/scale-from-zero/README.md index 0d0a9b7d55ea..7c4dd749b4c7 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scale-from-zero?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/scaled-registry/README.md b/examples/features/scaled-registry/README.md index 84acf425a798..6b744f956f71 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scaled-registry?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for NSE to be ready: diff --git a/examples/features/select-forwarder/README.md b/examples/features/select-forwarder/README.md index 1aa415b1b9cb..75ed1f4e13e6 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/select-forwarder?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/vl3-dns/README.md b/examples/features/vl3-dns/README.md index 442aaf6abf9c..50c8ffaedcce 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-dns?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for clients to be ready: diff --git a/examples/features/vl3-ipv6/README.md b/examples/features/vl3-ipv6/README.md index 3359938611c2..356d24b0d8a0 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-ipv6?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for clients to be ready: diff --git a/examples/features/vl3-lb/README.md b/examples/features/vl3-lb/README.md index d8f9d38d4020..36cdd7621ee0 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-lb?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 d649bed70d9a..db1d42100f63 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-scale-from-zero?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/webhook-smartvf/README.md b/examples/features/webhook-smartvf/README.md index 5afe1e6196ac..6335938f86f9 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook-smartvf?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/features/webhook/README.md b/examples/features/webhook/README.md index 14d76c56938d..d4083234496c 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/dataplane-interrupt/README.md b/examples/heal/dataplane-interrupt/README.md index 62f42f55752d..81914f5d345b 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/dataplane-interrupt?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/local-forwarder-death/README.md b/examples/heal/local-forwarder-death/README.md index 8b47acf16e53..36c867720c9b 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 00ec92a57ea7..7c0e0876ec47 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-remote-forwarder?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/local-nse-death/README.md b/examples/heal/local-nse-death/README.md index 65041321e660..74c522b65f83 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-before-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-after-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Restore NSE pod: diff --git a/examples/heal/local-nsm-system-restart/README.md b/examples/heal/local-nsm-system-restart/README.md index 6f5e7167a4ab..e1d44e8ac13c 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsm-system-restart?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 1dbfcc0749a2..18fe4977bb68 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-forwarder-memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 1b31cfcfb11e..14478d2456c9 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-before-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-after-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 c9fe3bb727e5..7ed84c2cee33 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-remote-nsmgr?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/local-nsmgr-restart/README.md b/examples/heal/local-nsmgr-restart/README.md index 40a40daf20a4..0339def65c77 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-restart?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/registry-local-endpoint/README.md b/examples/heal/registry-local-endpoint/README.md index e57b46291942..286318e1c271 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-first?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-second?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Waiting for new ones: diff --git a/examples/heal/registry-remote-forwarder/README.md b/examples/heal/registry-remote-forwarder/README.md index 8fc6122979bc..cbda19b6211f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-forwarder?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/registry-remote-nsmgr/README.md b/examples/heal/registry-remote-nsmgr/README.md index 1c44552f0b02..0e41ad1fe742 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-nsmgr?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/registry-restart/README.md b/examples/heal/registry-restart/README.md index a73d65e59209..2a8fc2347f66 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-before-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-after-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 796f0d350821..3ea0c783e4ab 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death-ip?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/remote-forwarder-death/README.md b/examples/heal/remote-forwarder-death/README.md index 11d0a3af0eaa..e433a9ef8bd6 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 efcb1dce2eeb..2e951d3fd705 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-before-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-after-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 bb0e4bf69b12..b5a9c6e8a177 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-before-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-after-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 8c99b7ad9c18..a3e09fcafa69 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsm-system-restart-memif-ip?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Ping from NSC to NSE: diff --git a/examples/heal/remote-nsmgr-death/README.md b/examples/heal/remote-nsmgr-death/README.md index e17d397a42b5..b71346ce0a0b 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/remote-nse?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/nsmgr-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/local-nse?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 -n nsm-system +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/nsmgr?ref=37a7407b8fbfe6620c868366006c3e722d33f38e -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 e6d1274d8091..99ab37c9c539 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-before-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-after-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 4546525c819c..7d27b328011a 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart-ip?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/remote-nsmgr-restart/README.md b/examples/heal/remote-nsmgr-restart/README.md index d6f087a81b2d..007991b3dd2d 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/spire-agent-restart/README.md b/examples/heal/spire-agent-restart/README.md index e6915cee62fa..c62268ae6410 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-agent-restart?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 050cf9946f10..d66a62f9d784 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-agent-restart?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/spire-server-restart/README.md b/examples/heal/spire-server-restart/README.md index 3c7b4c7b5543..c0f66168e78e 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-restart?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/heal/spire-upgrade/README.md b/examples/heal/spire-upgrade/README.md index da50ed509f70..a58a66b15e80 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-upgrade?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 f7e64225e381..cbbb216cc48f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nscs-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 1532343bb2d3..92f1edbf4b7a 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nse-death?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 e2c498741136..1a79f2007937 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal_extended/component-restart?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 fb4708729840..507ca2d1f4d4 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 41b36782c7d3..8eb90e8bc9da 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 99f08b54c5b0..fede861ebad9 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 c39ca63a2525..576fde5a4c42 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster1-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster2-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 4906c0f69b50..9bb76574ffa3 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md index 372d9f0195fb..12e414266d2f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md index 24c0bb8ab8d1..c6a7913c354b 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md index 5cba6eaf34d1..566cdec86cb2 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md index b8845eecd487..05d19fc89bdf 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md index 4193b00c72d0..9d92ae49a5f7 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md index 2328d5f370b5..bfa0f5462a4f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md b/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md index 06bcfde4566e..04a5e21a3dc5 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_dns/README.md b/examples/interdomain/usecases/floating_dns/README.md index 77679bc04717..b7a95c2fef69 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 50be442305e4..a1728328854c 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 0bd5c13ccea4..28cc4ea73e0e 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` diff --git a/examples/interdomain/usecases/floating_vl3-dns/README.md b/examples/interdomain/usecases/floating_vl3-dns/README.md index c7c84b61af72..b436a2d16d46 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 2. Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 3. Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 eb61b6f5cddc..372984c43fe1 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` diff --git a/examples/interdomain/usecases/heal_floating-forwarder-death/README.md b/examples/interdomain/usecases/heal_floating-forwarder-death/README.md index 438f486bfc0e..c933035d6048 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 50ab5ba29e3c..81838094a692 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 61dbaf39d55a..533d63e9ac6a 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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 2b98d60e40c9..3ce2ed24d3cf 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 ad5377e73036..23f17d416243 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 d2a2ccdf3fe3..53ce729151a1 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md index c6185491aa12..aeb213f3b585 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md index 0f5e55a21b67..86ebf80f4af8 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_dns/README.md b/examples/interdomain/usecases/interdomain_dns/README.md index 227f4944356b..9d30f8844858 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` **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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/nsm_consul/README.md b/examples/interdomain/usecases/nsm_consul/README.md index 1334efabfeba..35dabea502bc 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/server/counting.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-client?ref=37a7407b8fbfe6620c868366006c3e722d33f38e +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Create kubernetes service for the networkservicemesh proxy-endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/client/dashboard.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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=37a7407b8fbfe6620c868366006c3e722d33f38e +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=37a7407b8fbfe6620c868366006c3e722d33f38e +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 1882adcdef05..aa9afc72a4a4 100644 --- a/examples/interdomain/usecases/nsm_consul_vl3/README.md +++ b/examples/interdomain/usecases/nsm_consul_vl3/README.md @@ -14,11 +14,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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for pods to be ready: @@ -547,9 +547,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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` diff --git a/examples/interdomain/usecases/nsm_istio/README.md b/examples/interdomain/usecases/nsm_istio/README.md index 990a566c8a4d..073dd51780db 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio/nse-auto-scale?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio/greeting/server.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio/greeting/client.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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=37a7407b8fbfe6620c868366006c3e722d33f38e +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 4e8ec7eb6eca..a7cc7a75d7e1 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio_booking/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio_booking/nse-auto-scale?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/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=37a7407b8fbfe6620c868366006c3e722d33f38e +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 17a90f23ca7f..7c8a6c36940f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_kuma_universal_vl3/vl3-dns?ref=37a7407b8fbfe6620c868366006c3e722d33f38e 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_kuma_universal_vl3/namespace.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_kuma_universal_vl3/patch-control-plane.yaml +- path: https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-redis.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-app.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 41c1f60d4136..cedee14e061d 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ipsec_mechanism?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/k8s_monolith/external_nsc/README.md b/examples/k8s_monolith/external_nsc/README.md index c4df5af435c8..63c24174a07a 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 c33eebf4cde4..018a01cb011b 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/apps/nsc-simple-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 a995a02235b1..72092126c80b 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 4b636d8e568e..048fb30452c0 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/k8s_monolith/external_nse/README.md b/examples/k8s_monolith/external_nse/README.md index 3fab1bbd42fa..d030dd320422 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 04f8384fd45a..4b0b80ccbf16 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/apps/nse-simple-vl3-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 866f4c65093c..1aade09df3a3 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 12ba22fa5e5b..7f56fcd757dc 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Ethernet2Kernel/README.md b/examples/memory/Kernel2Ethernet2Kernel/README.md index 1024608c9685..210ae1ca02cb 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Ethernet2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Kernel/README.md b/examples/memory/Kernel2Kernel/README.md index a7038562319e..93cbaaae5089 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/memory/Memif2Memif/README.md b/examples/memory/Memif2Memif/README.md index de265e8d6f14..c0e8df8f8162 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Memif2Memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/memory/README.md b/examples/memory/README.md index 3a44f57a67d0..301b4c5cc535 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder/README.md b/examples/multiforwarder/README.md index 6a794041103b..f8ee127e2c75 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder_vlantag/README.md b/examples/multiforwarder_vlantag/README.md index fb85b84f1dfd..89e2f35f8d3a 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/observability/dashboard/README.md b/examples/observability/dashboard/README.md index 10b1e2dbcebc..93ac394d32ae 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/dashboard?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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 9837b98b5c5e..aceeb0c570b9 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus/example?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/observability/nsm_system/README.md b/examples/observability/nsm_system/README.md index fde1d657af51..44704cc1311e 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/nsm_system?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/ovs/README.md b/examples/ovs/README.md index 51e47348da4b..37e045472486 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ovs?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/README.md b/examples/pss/README.md index ee89f143babe..f7d8869191df 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/nsm-system?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/use-cases/nginx/README.md b/examples/pss/use-cases/nginx/README.md index 31862b3712ae..f2454ea72420 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/use-cases/nginx?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/remotevlan_ovs/README.md b/examples/remotevlan_ovs/README.md index 0410f29e31d6..fec9392f3888 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_ovs?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for NSE application: diff --git a/examples/remotevlan_vpp/README.md b/examples/remotevlan_vpp/README.md index 304478c324a8..24a78c751623 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_vpp?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for NSE application: diff --git a/examples/spire/cluster1/README.md b/examples/spire/cluster1/README.md index 4009a2ed4bde..b9d1cfff44ec 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/cluster1/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/cluster1/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster2/README.md b/examples/spire/cluster2/README.md index 1c5375691ece..11bec062ffb0 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/cluster2/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/cluster2/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster3/README.md b/examples/spire/cluster3/README.md index 89c1a61abae2..1937f1334c4b 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/cluster3/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/cluster3/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 a37291b5efaf..1bf2d6314c68 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/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 9afd28657804..c0bdce8c1c73 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster_csi?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/sriov/README.md b/examples/sriov/README.md index 06e01c232bbc..487ea7d84f13 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ## Includes diff --git a/examples/sriov_vlantag/README.md b/examples/sriov_vlantag/README.md index d0b7c1a10775..8f1614ca4f2f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` ## Includes diff --git a/examples/use-cases/Kernel2Ethernet2Kernel/README.md b/examples/use-cases/Kernel2Ethernet2Kernel/README.md index d8c5cce3b18c..e982ede60210 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md index a34cd5eb75f4..aa82e3e4cd97 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md index 60cabb129d11..b28de84c8969 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Memif/README.md b/examples/use-cases/Kernel2Ethernet2Memif/README.md index 0b88ca8bac3b..c6353d123973 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Kernel/README.md b/examples/use-cases/Kernel2IP2Kernel/README.md index fd4026e5feaa..fa4e8f00b642 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Memif/README.md b/examples/use-cases/Kernel2IP2Memif/README.md index f59088163257..1d3d4e4a89bc 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel/README.md b/examples/use-cases/Kernel2Kernel/README.md index 408b10b91aa4..f1d1c26b9ec7 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2KernelVLAN/README.md b/examples/use-cases/Kernel2KernelVLAN/README.md index 435afba2f5a5..f42f11c9ee38 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2KernelVLAN?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md index 714ea94316af..47cd7b52021f 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2Noop?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md index 4608e36c899a..4e8bf2589aaf 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Memif/README.md b/examples/use-cases/Kernel2Memif/README.md index 7219bd1ebf91..4c1a635589f2 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanBreakout/README.md b/examples/use-cases/Kernel2RVlanBreakout/README.md index 4014eb4f8ed6..06220855534a 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanBreakout?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanInternal/README.md b/examples/use-cases/Kernel2RVlanInternal/README.md index 367fc6e50c9b..6a34e59270ef 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanInternal?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanMultiNS/README.md b/examples/use-cases/Kernel2RVlanMultiNS/README.md index be484338e308..b403ad495627 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Deployment in second namespace: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Deployment in third namespace: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Kernel/README.md b/examples/use-cases/Memif2Ethernet2Kernel/README.md index 2bbacbdbfc96..fe68629958b9 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Memif/README.md b/examples/use-cases/Memif2Ethernet2Memif/README.md index dfc4726443d4..4aac93d937dc 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Kernel/README.md b/examples/use-cases/Memif2IP2Kernel/README.md index 5f093485a9f5..4b440cdfd836 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Memif/README.md b/examples/use-cases/Memif2IP2Memif/README.md index c8df6c00c7b9..09f30ddc9733 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Kernel/README.md b/examples/use-cases/Memif2Kernel/README.md index 91659433ee7c..6bdd4084c24b 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Kernel?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Memif/README.md b/examples/use-cases/Memif2Memif/README.md index e6d4a3b76e65..77cc494d0af4 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Memif?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/SmartVF2SmartVF/README.md b/examples/use-cases/SmartVF2SmartVF/README.md index da3cdbd44763..f5fc5bad7973 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SmartVF2SmartVF?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2Noop/README.md b/examples/use-cases/SriovKernel2Noop/README.md index 093cefe6a546..ba47f2d28c34 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2NoopVlanTag/README.md b/examples/use-cases/SriovKernel2NoopVlanTag/README.md index a8e1a974fed1..21505c0bc453 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag/ponger?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2Noop/README.md b/examples/use-cases/Vfio2Noop/README.md index 60907c04fccd..0b8864b964db 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2Noop?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2NoopVlanTag/README.md b/examples/use-cases/Vfio2NoopVlanTag/README.md index c9b53d4f67e6..a87b1d2d0e12 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2NoopVlanTag?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for applications ready: diff --git a/examples/use-cases/vl3-basic/README.md b/examples/use-cases/vl3-basic/README.md index 6ad4a1675550..868455616570 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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/vl3-basic?ref=37a7407b8fbfe6620c868366006c3e722d33f38e ``` Wait for clients to be ready: diff --git a/to-ref.sh b/to-ref.sh index 76cfe09f5146..c0937af8c8fe 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/54e0ba111979c4d42fd91e3f0bd4453e5f725b69/\1')" +FILE_PATTERN="$(escape 'https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/37a7407b8fbfe6620c868366006c3e722d33f38e/\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=54e0ba111979c4d42fd91e3f0bd4453e5f725b69')" +DIR_PATTERN="$(escape 'https://github.com/networkservicemesh/deployments-k8s/\1?ref=37a7407b8fbfe6620c868366006c3e722d33f38e')" grep "$(pwd)" -rl examples/* | while IFS= read -r file; do root="$(get_root "$file")" sedi -E "s/${root//./\.}\/([^ ]*)/${DIR_PATTERN}/g" "${file}"