From da37c9603a225f66d9371d4c302b84ff01f2f255 Mon Sep 17 00:00:00 2001 From: nsmbot Date: Wed, 6 Nov 2024 14:27:36 +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 303d8243df7..22d00cba325 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/afxdp?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/basic/README.md b/examples/basic/README.md index b1939aefbac..82f046db2d2 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/features/annotated-namespace/README.md b/examples/features/annotated-namespace/README.md index 2d64ab3b9f4..a099eead21b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/annotated-namespace?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/features/annotated-namespace/client.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 64eebbdb98e..33f57a27f83 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/change-nse-dynamically?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/features/change-nse-dynamically/green-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/features/change-nse-dynamically/blue-netsvc.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 1f6b7da1131..6926b4a545d 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dns?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 14d4c8d12f3..f7df69687d7 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 241923fb96d..159365feffb 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2Kernel_dual_stack?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 cb34112eb93..37c1c317921 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/vl3-dual-stack/ipam-ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 8b19a02d802..16a7f00e3b3 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes-client?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/exclude-prefixes/README.md b/examples/features/exclude-prefixes/README.md index 92858158bda..a53403bc082 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes/configmap?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/ipam-policies/README.md b/examples/features/ipam-policies/README.md index c8656c92f1d..3b76d440f45 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/29` and `default` IPAM Policy: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipam-policies?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipam-policies?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: @@ -58,7 +58,7 @@ kubectl delete pod -l app=first-nse -n ns-ipam-policies Apply the second NSE with CIDR `172.16.2.0/29` and `strict` IPAM Policy: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/features/ipam-policies/second-nse.yaml -n ns-ipam-policies +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/features/ipam-policies/second-nse.yaml -n ns-ipam-policies ``` Wait for application ready: diff --git a/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md index 0eba92245f2..2325b6eef23 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Kernel_ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md index 8ca51de08f8..2f1abfe6f30 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Memif_ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2Kernel_ipv6/README.md index c29af002de5..50d83efd9e8 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2Kernel_ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md index f1f43de6456..c082e88807f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Kernel_ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md b/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md index 8330e3ce779..5bccb801e37 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Memif_ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2Memif_ipv6/README.md b/examples/features/ipv6/Memif2Memif_ipv6/README.md index f0ada86a760..60e0f765f9d 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2Memif_ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/jaeger/README.md b/examples/features/jaeger/README.md index 83554b5b65c..c1e0426272f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/jaeger?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/opentelemetry?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Apply Spire deployments (required for NSM system) ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/nsm-system?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/features/multiple-services/README.md b/examples/features/multiple-services/README.md index 38adf353449..77f0982afd3 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/multiple-services?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/mutually-aware-nses/README.md b/examples/features/mutually-aware-nses/README.md index 21840987c2a..4bc4bc17a79 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/mutually-aware-nses?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/nse-composition/README.md b/examples/features/nse-composition/README.md index a652a0fd099..597fc18b793 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/nse-composition?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/opa/README.md b/examples/features/opa/README.md index 7040c63ea3b..cdd7767cf46 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/opa?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/policy-based-routing/README.md b/examples/features/policy-based-routing/README.md index 80401c44503..8f701c2c728 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/policy-based-routing?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/scale-from-zero/README.md b/examples/features/scale-from-zero/README.md index 20be939bbb4..debb7fe6f9b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scale-from-zero?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/scaled-registry/README.md b/examples/features/scaled-registry/README.md index d95b1a9efa8..5224e28ea19 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scaled-registry?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for NSE to be ready: diff --git a/examples/features/select-forwarder/README.md b/examples/features/select-forwarder/README.md index f85fc944281..3f2dcf10f15 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/select-forwarder?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/vl3-dns/README.md b/examples/features/vl3-dns/README.md index d051bc1c5c1..14ab1f758f6 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-dns?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for clients to be ready: diff --git a/examples/features/vl3-ipv6/README.md b/examples/features/vl3-ipv6/README.md index 5eedc5126c0..09d7442877f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-ipv6?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for clients to be ready: diff --git a/examples/features/vl3-lb/README.md b/examples/features/vl3-lb/README.md index 458cd42240a..0af621cae68 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-lb?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 91e8e90baba..efaaece0b20 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-scale-from-zero?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/webhook-smartvf/README.md b/examples/features/webhook-smartvf/README.md index b6901c49777..f6e90d5fd72 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook-smartvf?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/features/webhook/README.md b/examples/features/webhook/README.md index c9bd9f375cb..954680b2e62 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/dataplane-interrupt/README.md b/examples/heal/dataplane-interrupt/README.md index 94a01535c2e..82b68a1cb19 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/dataplane-interrupt?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/local-forwarder-death/README.md b/examples/heal/local-forwarder-death/README.md index 67aa9d2cbbd..7efc68c1480 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 dbfd8926ddc..4a117be8181 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-remote-forwarder?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/local-nse-death/README.md b/examples/heal/local-nse-death/README.md index 150bd1d1617..cb43292c766 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-before-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-after-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Restore NSE pod: diff --git a/examples/heal/local-nsm-system-restart/README.md b/examples/heal/local-nsm-system-restart/README.md index 08633999254..38594ba246b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsm-system-restart?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 a9e48bd48ba..16eee7a0f1e 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-forwarder-memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 d75388b0ee3..c57160bb2db 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-before-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-after-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 d1ea6ce3f2a..5798b2f2b47 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-remote-nsmgr?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/local-nsmgr-restart/README.md b/examples/heal/local-nsmgr-restart/README.md index afebcd71f8d..1de8ece0dfe 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-restart?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/registry-local-endpoint/README.md b/examples/heal/registry-local-endpoint/README.md index 0a6647871b6..7715dc83b90 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-first?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-second?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Waiting for new ones: diff --git a/examples/heal/registry-remote-forwarder/README.md b/examples/heal/registry-remote-forwarder/README.md index b5a22860928..aea0394d81c 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-forwarder?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/registry-remote-nsmgr/README.md b/examples/heal/registry-remote-nsmgr/README.md index 53fac0383b3..217ed4989e6 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-nsmgr?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/registry-restart/README.md b/examples/heal/registry-restart/README.md index 94f8e79aaa0..8efc7542d9e 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-before-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-after-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 b2521f2d463..58672a65008 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death-ip?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/remote-forwarder-death/README.md b/examples/heal/remote-forwarder-death/README.md index b7b813d17b0..44c6272dd23 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 b5579c8103e..f1675458af5 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-before-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-after-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 118b17c5a02..418bd930074 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-before-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-after-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 e9f2ccfb52d..bf507e27e47 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsm-system-restart-memif-ip?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Ping from NSC to NSE: diff --git a/examples/heal/remote-nsmgr-death/README.md b/examples/heal/remote-nsmgr-death/README.md index e663a8528d5..7e5b200a61b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/remote-nse?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/nsmgr-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/local-nse?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c -n nsm-system +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/nsmgr?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 -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 3fb4e3ab156..c4b47f97e9f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-before-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-after-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 082220204b1..07a8544f819 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart-ip?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/remote-nsmgr-restart/README.md b/examples/heal/remote-nsmgr-restart/README.md index 3d38cc1226d..d00e21290bd 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/spire-agent-restart/README.md b/examples/heal/spire-agent-restart/README.md index b2cbc1231d1..315be4b33e4 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-agent-restart?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 bea80de4173..c3405c0d9da 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-agent-restart?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/spire-server-restart/README.md b/examples/heal/spire-server-restart/README.md index 12cad78e8df..9e9d82b02f0 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-restart?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/heal/spire-upgrade/README.md b/examples/heal/spire-upgrade/README.md index e47b84609e9..4fe88b7be37 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-upgrade?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 1c797eb5373..7ae341e1055 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nscs-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 5f598d58a82..552169840ff 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nse-death?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 5d053021efc..80ba748e459 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal_extended/component-restart?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 545206e35d5..dcbfb214bc4 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 029adfecf1a..d3bf2b441f0 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/ipsec/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 34fb207af64..43f5c127805 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/two_cluster_configuration/basic/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 ac3ad204e9b..b5a7df4eff6 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster1-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/two_cluster_configuration/spiffe_federation/cluster2-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 936a523f7f5..0d0945a919c 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Kernel/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/README.md index a8c11f10bf3..622e8cef801 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2Ethernet2Memif/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Kernel/README.md index a85ad08b3fd..b809c00cfa6 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Kernel/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md b/examples/interdomain/usecases/floating_Kernel2IP2Memif/README.md index ef89f0a62d9..a19a374e31b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Kernel2IP2Memif/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/README.md index cff5a43c4c2..bad497efb67 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Kernel/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md b/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/README.md index 779f99a584e..985e9dc0d97 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2Ethernet2Memif/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md b/examples/interdomain/usecases/floating_Memif2IP2Kernel/README.md index 288717a3082..c6ee7f49288 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Kernel/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md b/examples/interdomain/usecases/floating_Memif2IP2Memif/README.md index b238052b318..9b804ee3a51 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_Memif2IP2Memif/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/floating_dns/README.md b/examples/interdomain/usecases/floating_dns/README.md index 5298c871cdc..30b8cefed79 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_dns/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 0fd184de714..f002d187f0f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_nse_composition/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 4f1b43b39c5..1e3057def1c 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-basic/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` diff --git a/examples/interdomain/usecases/floating_vl3-dns/README.md b/examples/interdomain/usecases/floating_vl3-dns/README.md index 8dd732e05ee..0dc86bb06c4 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 2. Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 3. Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-dns/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 1c3eba867ce..b29b4880b19 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/floating_vl3-scale-from-zero/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` diff --git a/examples/interdomain/usecases/heal_floating-forwarder-death/README.md b/examples/interdomain/usecases/heal_floating-forwarder-death/README.md index dcde127d77f..804fae8d222 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-forwarder-death/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 1dcfb8e6245..f5539073da0 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nse-death/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 1369466cf22..633f77bd22a 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_floating-nsm-system-death/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/three_cluster_configuration/basic/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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 ee46f929883..e474c204011 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-nsmgr-death/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 bf62f30b9e8..c93e388d057 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-proxy-nsmgr-death/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 1dc7b2c25b9..06e1b2054d1 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/heal_interdomain-registry-death/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/README.md index ec5b368f7b3..80b21e204c8 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2Ethernet2Kernel/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md b/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/README.md index 270e37f2670..21e9ed9f355 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_Kernel2IP2Kernel/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/interdomain_dns/README.md b/examples/interdomain/usecases/interdomain_dns/README.md index f3fe671d522..811eea778f6 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` **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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/interdomain_dns/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/interdomain/usecases/nsm_consul/README.md b/examples/interdomain/usecases/nsm_consul/README.md index a1b753f9b21..7dd611283fe 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/server/counting.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-client?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Create kubernetes service for the networkservicemesh proxy-endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/client/dashboard.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/interdomain/usecases/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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=36fdb60145f4449cf76c20feb6b606631a5d8694 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul/nse-auto-scale-server?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/interdomain/usecases/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/interdomain/usecases/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 24d505d1598..598e84a2dd3 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_consul_vl3/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` diff --git a/examples/interdomain/usecases/nsm_istio/README.md b/examples/interdomain/usecases/nsm_istio/README.md index 9ef9789935a..45738a1f283 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio/nse-auto-scale?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio/greeting/server.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio/greeting/client.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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=36fdb60145f4449cf76c20feb6b606631a5d8694 +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/interdomain/usecases/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 9f37327699d..ced129648e1 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio_booking/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_istio_booking/nse-auto-scale?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/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=36fdb60145f4449cf76c20feb6b606631a5d8694 +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/interdomain/usecases/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 ffb0ba70284..212ba035088 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/usecases/nsm_kuma_universal_vl3/vl3-dns?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_kuma_universal_vl3/namespace.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_kuma_universal_vl3/patch-control-plane.yaml +- path: https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-redis.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/interdomain/usecases/nsm_kuma_universal_vl3/demo-app.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 984dfe92884..3d2a6ac113f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ipsec_mechanism?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/k8s_monolith/external_nsc/README.md b/examples/k8s_monolith/external_nsc/README.md index e76b94f5681..4516f4d52df 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 664226a6a73..58907a1b712 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/apps/nsc-simple-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 df85809e3fe..50698092b0c 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 e27450adfef..fd717e0b6d6 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/k8s_monolith/external_nse/README.md b/examples/k8s_monolith/external_nse/README.md index 48d476f6824..41c01e10014 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 f4e8acabc5d..55d81e10cc7 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/apps/nse-simple-vl3-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 528b143e8aa..de135b6ac21 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 f7707b593c9..8fe146051db 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Ethernet2Kernel/README.md b/examples/memory/Kernel2Ethernet2Kernel/README.md index e783bcc0326..bab1511c967 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Ethernet2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Kernel/README.md b/examples/memory/Kernel2Kernel/README.md index eaf73f67250..2e726474436 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/memory/Memif2Memif/README.md b/examples/memory/Memif2Memif/README.md index 93ae81de9f6..52aade42819 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Memif2Memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/memory/README.md b/examples/memory/README.md index bb7e9b2cbb8..14fb0b84598 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder/README.md b/examples/multiforwarder/README.md index 8ceb1c14850..cf430058274 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder_vlantag/README.md b/examples/multiforwarder_vlantag/README.md index 21e1bcc606f..62dcce20907 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/observability/dashboard/README.md b/examples/observability/dashboard/README.md index 952ab0c638f..f8bb3258095 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/dashboard?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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 f6eb2c0fe0c..fabf87658fa 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger_and_prometheus/example?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/observability/nsm_system/README.md b/examples/observability/nsm_system/README.md index 5dccaaf3bcf..14913314138 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/nsm_system?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/ovs/README.md b/examples/ovs/README.md index 4d3787d96f9..65fce4a5234 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ovs?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/README.md b/examples/pss/README.md index 5ba5d847800..a8404545526 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/nsm-system?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/use-cases/nginx/README.md b/examples/pss/use-cases/nginx/README.md index 8246057b6ed..9669d0977ba 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/use-cases/nginx?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/remotevlan_ovs/README.md b/examples/remotevlan_ovs/README.md index 01b78759eba..16393cc5e7b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_ovs?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for NSE application: diff --git a/examples/remotevlan_vpp/README.md b/examples/remotevlan_vpp/README.md index 389ac431508..fcc7c25a141 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_vpp?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for NSE application: diff --git a/examples/spire/cluster1/README.md b/examples/spire/cluster1/README.md index 62313db2f57..222b24802aa 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/cluster1/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/cluster1/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster2/README.md b/examples/spire/cluster2/README.md index 51cb677a217..1dae3df5f3b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/cluster2/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/cluster2/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster3/README.md b/examples/spire/cluster3/README.md index bc78ef541e3..444f64825c1 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/cluster3/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/cluster3/clusterspiffeid-template.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 451271e091e..e7f3d5d3649 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/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 7b511de2e22..854edbe548e 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster_csi?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/spire/base/clusterspiffeid-webhook-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/spire/base/clusterspiffeid-webhook-template.yaml ``` ## Cleanup diff --git a/examples/sriov/README.md b/examples/sriov/README.md index 12c55058856..e607ccf5c6b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ## Includes diff --git a/examples/sriov_vlantag/README.md b/examples/sriov_vlantag/README.md index f71ad5b23cc..c0ef574093c 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` ## Includes diff --git a/examples/use-cases/Kernel2Ethernet2Kernel/README.md b/examples/use-cases/Kernel2Ethernet2Kernel/README.md index d13411ce0ba..8d661e9469f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md index 10b45d6995f..9208cb24204 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md index 0f92e4d880f..fc0e457375d 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Memif/README.md b/examples/use-cases/Kernel2Ethernet2Memif/README.md index 3822be58f06..6a97218c867 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Kernel/README.md b/examples/use-cases/Kernel2IP2Kernel/README.md index c60b6349d66..75a0531e4c8 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Memif/README.md b/examples/use-cases/Kernel2IP2Memif/README.md index 975b5f4ae9b..80c53c6153e 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel/README.md b/examples/use-cases/Kernel2Kernel/README.md index fdc6bbb3abb..db208f7cd77 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2KernelVLAN/README.md b/examples/use-cases/Kernel2KernelVLAN/README.md index dec0e28f2ca..3759cb03bf3 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2KernelVLAN?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md index e89353630c3..da7ee8c6429 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2Noop?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md index bfcb014a0cb..b5a7a9f43d0 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Memif/README.md b/examples/use-cases/Kernel2Memif/README.md index b5ae4bcb9d1..6fa20bf965a 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanBreakout/README.md b/examples/use-cases/Kernel2RVlanBreakout/README.md index 851621358d4..7b84202cd7f 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanBreakout?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanInternal/README.md b/examples/use-cases/Kernel2RVlanInternal/README.md index 74ce930d701..880372e54bc 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanInternal?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanMultiNS/README.md b/examples/use-cases/Kernel2RVlanMultiNS/README.md index 54db9514526..c566d99e3b9 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Deployment in second namespace: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Deployment in third namespace: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-3?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Kernel/README.md b/examples/use-cases/Memif2Ethernet2Kernel/README.md index 13d9d9e0420..cd039508f23 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Memif/README.md b/examples/use-cases/Memif2Ethernet2Memif/README.md index a1cbde1004d..0c71c39bb6b 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Kernel/README.md b/examples/use-cases/Memif2IP2Kernel/README.md index 247b3525312..a72c26e05cf 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Memif/README.md b/examples/use-cases/Memif2IP2Memif/README.md index ed983f9c20d..0d02d7b2ffd 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Kernel/README.md b/examples/use-cases/Memif2Kernel/README.md index 7fc20a224f1..3d94bf409e3 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Kernel?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Memif/README.md b/examples/use-cases/Memif2Memif/README.md index 43c43fd5924..b7a9fc0f5d4 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Memif?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/SmartVF2SmartVF/README.md b/examples/use-cases/SmartVF2SmartVF/README.md index 59646e5a36d..9eef0ededfb 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SmartVF2SmartVF?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2Noop/README.md b/examples/use-cases/SriovKernel2Noop/README.md index 0565df7f1af..83e3243b4e9 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2NoopVlanTag/README.md b/examples/use-cases/SriovKernel2NoopVlanTag/README.md index 3700ed0749f..1446e80708a 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag/ponger?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2Noop/README.md b/examples/use-cases/Vfio2Noop/README.md index d7808a0dc21..06513c8d1d3 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2Noop?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2NoopVlanTag/README.md b/examples/use-cases/Vfio2NoopVlanTag/README.md index dfb1964306d..dcf3fe860d2 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2NoopVlanTag?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for applications ready: diff --git a/examples/use-cases/vl3-basic/README.md b/examples/use-cases/vl3-basic/README.md index df77b5b2821..47943f88c26 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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/vl3-basic?ref=36fdb60145f4449cf76c20feb6b606631a5d8694 ``` Wait for clients to be ready: diff --git a/to-ref.sh b/to-ref.sh index 428fb0bc498..56ada63fab4 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/af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c/\1')" +FILE_PATTERN="$(escape 'https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/36fdb60145f4449cf76c20feb6b606631a5d8694/\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=af0551eb46fab72ab9a7eb94ae38bc87c2e5c07c')" +DIR_PATTERN="$(escape 'https://github.com/networkservicemesh/deployments-k8s/\1?ref=36fdb60145f4449cf76c20feb6b606631a5d8694')" grep "$(pwd)" -rl examples/* | while IFS= read -r file; do root="$(get_root "$file")" sedi -E "s/${root//./\.}\/([^ ]*)/${DIR_PATTERN}/g" "${file}"