From a6c9064dc7cb250a628a4a85be9f1b6c721dcf05 Mon Sep 17 00:00:00 2001 From: NSMBot Date: Tue, 29 Aug 2023 14:56:48 +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 +-- examples/features/dns/README.md | 2 +- .../Kernel2IP2Kernel_dual_stack/README.md | 2 +- .../Kernel2Kernel_dual_stack/README.md | 2 +- .../exclude-prefixes-client/README.md | 2 +- examples/features/exclude-prefixes/README.md | 4 +-- .../ipv6/Kernel2IP2Kernel_ipv6/README.md | 2 +- .../ipv6/Kernel2IP2Memif_ipv6/README.md | 2 +- .../ipv6/Kernel2Kernel_ipv6/README.md | 2 +- .../ipv6/Memif2IP2Kernel_ipv6/README.md | 2 +- .../ipv6/Memif2IP2Memif_ipv6/README.md | 2 +- .../features/ipv6/Memif2Memif_ipv6/README.md | 2 +- examples/features/jaeger/README.md | 8 ++--- examples/features/multiple-services/README.md | 2 +- .../features/mutually-aware-nses/README.md | 2 +- examples/features/nse-composition/README.md | 2 +- examples/features/opa/README.md | 2 +- .../features/policy-based-routing/README.md | 2 +- examples/features/scale-from-zero/README.md | 2 +- examples/features/select-forwarder/README.md | 2 +- examples/features/vl3-basic/README.md | 2 +- examples/features/vl3-dns/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 | 6 ++-- examples/heal/vl3-nscs-death/README.md | 2 +- examples/heal/vl3-nse-death/README.md | 2 +- examples/interdomain/nsm/README.md | 8 ++--- examples/interdomain/nsm_consul/README.md | 30 +++++++++---------- examples/interdomain/nsm_istio/README.md | 16 +++++----- .../interdomain/nsm_istio_booking/README.md | 12 ++++---- .../nsm_kuma_universal_vl3/README.md | 10 +++---- .../interdomain/spiffe_federation/README.md | 4 +-- 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 | 2 +- .../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 | 2 +- .../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/multicluster/README.md | 6 ++-- .../floating_Kernel2Ethernet2Kernel/README.md | 6 ++-- .../floating_Kernel2IP2Kernel/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 ++++---- .../README.md | 4 +-- .../interdomain_Kernel2IP2Kernel/README.md | 4 +-- .../usecases/interdomain_dns/README.md | 4 +-- examples/multiforwarder/README.md | 2 +- examples/multiforwarder_vlantag/README.md | 2 +- .../jaeger-and-prometheus/README.md | 6 ++-- 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 | 4 +-- examples/spire/cluster2/README.md | 4 +-- examples/spire/cluster3/README.md | 4 +-- examples/spire/single_cluster/README.md | 4 +-- examples/spire/single_cluster_csi/README.md | 4 +-- 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 | 12 ++++---- .../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 +- to-ref.sh | 4 +-- 126 files changed, 222 insertions(+), 222 deletions(-) diff --git a/examples/afxdp/README.md b/examples/afxdp/README.md index 0695397dc62e..ddcf61ee529e 100644 --- a/examples/afxdp/README.md +++ b/examples/afxdp/README.md @@ -34,7 +34,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/afxdp?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/basic/README.md b/examples/basic/README.md index a240e55f8ade..57fc271d1751 100644 --- a/examples/basic/README.md +++ b/examples/basic/README.md @@ -26,7 +26,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/features/annotated-namespace/README.md b/examples/features/annotated-namespace/README.md index ddb808d42656..a4d71bc342f2 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/annotated-namespace?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/features/annotated-namespace/client.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/features/annotated-namespace/client.yaml ``` Wait for client to be ready: diff --git a/examples/features/dns/README.md b/examples/features/dns/README.md index b5dbd21665d6..cbc833832b93 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dns?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 9556e5e2bbda..c8947593d191 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2IP2Kernel_dual_stack?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 ddb5b2b1d14a..6a4f088972a5 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/dual-stack/Kernel2Kernel_dual_stack?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/exclude-prefixes-client/README.md b/examples/features/exclude-prefixes-client/README.md index a8cf63ced05e..0b17da24e33e 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes-client?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/exclude-prefixes/README.md b/examples/features/exclude-prefixes/README.md index b965a39c2958..60de17d05d05 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes/configmap?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/exclude-prefixes?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Kernel_ipv6/README.md index e238121b6491..cc422c1a1ebc 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Kernel_ipv6?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md b/examples/features/ipv6/Kernel2IP2Memif_ipv6/README.md index 772a4c77674c..2cb752b32972 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2IP2Memif_ipv6?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Kernel2Kernel_ipv6/README.md b/examples/features/ipv6/Kernel2Kernel_ipv6/README.md index 09eae07b4fde..da6d4310429e 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Kernel2Kernel_ipv6?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md b/examples/features/ipv6/Memif2IP2Kernel_ipv6/README.md index 299799c434a8..94b2fc7730d3 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Kernel_ipv6?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md b/examples/features/ipv6/Memif2IP2Memif_ipv6/README.md index d1f474565bdb..2e3bd773b2ba 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2IP2Memif_ipv6?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/ipv6/Memif2Memif_ipv6/README.md b/examples/features/ipv6/Memif2Memif_ipv6/README.md index 5a3437818f8e..070599cb4824 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/ipv6/Memif2Memif_ipv6?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/jaeger/README.md b/examples/features/jaeger/README.md index 52c1f0417634..266e97af48aa 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/jaeger?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/opentelemetry?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Apply Spire deployments (required for NSM system) ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/jaeger/nsm-system?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/features/multiple-services/README.md b/examples/features/multiple-services/README.md index 24e39e94f0f3..45c9e4b0314e 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/multiple-services?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/mutually-aware-nses/README.md b/examples/features/mutually-aware-nses/README.md index 7a2a33a9dd6f..af29730a8a44 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/mutually-aware-nses?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/nse-composition/README.md b/examples/features/nse-composition/README.md index 9134550f3766..4d39b5fcc6c1 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/nse-composition?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/opa/README.md b/examples/features/opa/README.md index 06a2f1e7f383..5c42116813a7 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/opa?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/policy-based-routing/README.md b/examples/features/policy-based-routing/README.md index af0b41e53196..b0b745abf197 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/policy-based-routing?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/scale-from-zero/README.md b/examples/features/scale-from-zero/README.md index c90b731c6fb1..515aba321531 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/scale-from-zero?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/select-forwarder/README.md b/examples/features/select-forwarder/README.md index 26587d25fd5f..f93724662e7d 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/select-forwarder?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/vl3-basic/README.md b/examples/features/vl3-basic/README.md index 8dfcbcdd379b..9223dbd745ed 100644 --- a/examples/features/vl3-basic/README.md +++ b/examples/features/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/features/vl3-basic?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-basic?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for clients to be ready: diff --git a/examples/features/vl3-dns/README.md b/examples/features/vl3-dns/README.md index 33f4edee68ab..27246a8c8c68 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-dns?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for 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 327a1598b8b6..7bd729910b5c 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/vl3-scale-from-zero?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/webhook-smartvf/README.md b/examples/features/webhook-smartvf/README.md index b1eb490fba53..38172b6880e5 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook-smartvf?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/features/webhook/README.md b/examples/features/webhook/README.md index cfd41e41c1f8..5437a64b1f51 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/features/webhook?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/dataplane-interrupt/README.md b/examples/heal/dataplane-interrupt/README.md index 71266452749a..57e69491710f 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/dataplane-interrupt?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/local-forwarder-death/README.md b/examples/heal/local-forwarder-death/README.md index 53cd24bdc1de..66a1ad2500dd 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 f665b060dd8b..db635ea021db 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-forwarder-remote-forwarder?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/local-nse-death/README.md b/examples/heal/local-nse-death/README.md index e9a1b6a2f457..77b20b0f0f50 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-before-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nse-death/nse-after-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Restore NSE pod: diff --git a/examples/heal/local-nsm-system-restart/README.md b/examples/heal/local-nsm-system-restart/README.md index 7c47bd26c7b7..cfe1f1f9a745 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsm-system-restart?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: @@ -40,7 +40,7 @@ kubectl delete mutatingwebhookconfiguration ${WH} kubectl delete ns nsm-system ``` ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 ea7516153ec3..c16fec47a800 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-forwarder-memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 13d7caed2775..1431c0544978 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-before-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-local-nse-memif/nse-after-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 fa7364d79546..47b5ac4907a8 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-remote-nsmgr?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/local-nsmgr-restart/README.md b/examples/heal/local-nsmgr-restart/README.md index db298a89fddb..419ed2640882 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/local-nsmgr-restart?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/registry-local-endpoint/README.md b/examples/heal/registry-local-endpoint/README.md index 9877180b3b9d..f07307781379 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-first?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-local-endpoint/nse-second?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Waiting for new ones: diff --git a/examples/heal/registry-remote-forwarder/README.md b/examples/heal/registry-remote-forwarder/README.md index b49ec6dcfd0a..4a9d28b57635 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-forwarder?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/registry-remote-nsmgr/README.md b/examples/heal/registry-remote-nsmgr/README.md index c192382c3933..2e58bb0b09dc 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-remote-nsmgr?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/registry-restart/README.md b/examples/heal/registry-restart/README.md index b55e22a767b7..89573aafc991 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-before-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/registry-restart/registry-after-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 81be188f3853..585406fc568a 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death-ip?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/remote-forwarder-death/README.md b/examples/heal/remote-forwarder-death/README.md index 6875d8ec6893..058e411e3713 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-forwarder-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 68e25bd6adc8..e65f244e74be 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-before-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death-ip/nse-after-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 e9c6f63ac55c..968f1985f3a2 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-before-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nse-death/nse-after-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 cf55829988df..2810d030842b 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsm-system-restart-memif-ip?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: @@ -48,7 +48,7 @@ kubectl delete ns nsm-system kubectl create ns nsm-system ``` ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/basic?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Ping from NSC to NSE: diff --git a/examples/heal/remote-nsmgr-death/README.md b/examples/heal/remote-nsmgr-death/README.md index 60a82ebdfab6..7c640532bc88 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/remote-nse?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/nsmgr-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-death/local-nse?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d -n nsm-system +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/apps/nsmgr?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 -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 4cd748a55f45..467424465586 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-before-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-remote-endpoint/nsmgr-after-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 041ff82fc301..8c800bbbb597 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart-ip?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/remote-nsmgr-restart/README.md b/examples/heal/remote-nsmgr-restart/README.md index d7c0e2ad890b..394c0e5b4efb 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/remote-nsmgr-restart?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/spire-agent-restart/README.md b/examples/heal/spire-agent-restart/README.md index 7a3baf1bd3f7..aeb83f2ce375 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-agent-restart?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 88c3fa136527..2270ca459712 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-agent-restart?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/spire-server-restart/README.md b/examples/heal/spire-server-restart/README.md index 989be489d6b2..7944da4f40be 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-server-restart?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/heal/spire-upgrade/README.md b/examples/heal/spire-upgrade/README.md index 6207483e2e96..148501226656 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/spire-upgrade?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` ```bash @@ -61,7 +61,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/spire/single_cluster/clusterspiffeid-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 fe0e6104a01c..9e614fb38805 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nscs-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 1f7a9b1e14f5..f07891d07ac4 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/heal/vl3-nse-death?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for clients to be ready: diff --git a/examples/interdomain/nsm/README.md b/examples/interdomain/nsm/README.md index fbd40459bedf..d943781825cf 100644 --- a/examples/interdomain/nsm/README.md +++ b/examples/interdomain/nsm/README.md @@ -8,13 +8,13 @@ This example simply show how can be deployed and configured two NSM on different Create basic NSM deployment on cluster 1: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Create basic NSM deployment on cluster 2: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for NSM admission webhook on cluster 1: @@ -39,6 +39,6 @@ kubectl --kubeconfig=$KUBECONFIG1 delete mutatingwebhookconfiguration ${WH} WH=$(kubectl --kubeconfig=$KUBECONFIG2 get pods -l app=admission-webhook-k8s -n nsm-system --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}') kubectl --kubeconfig=$KUBECONFIG2 delete mutatingwebhookconfiguration ${WH} -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` diff --git a/examples/interdomain/nsm_consul/README.md b/examples/interdomain/nsm_consul/README.md index af1688e6d8ac..02631712e365 100644 --- a/examples/interdomain/nsm_consul/README.md +++ b/examples/interdomain/nsm_consul/README.md @@ -36,31 +36,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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/server/counting_service.yaml ``` ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/server/counting.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/server/counting.yaml ``` Deploy networkservice on the second cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/netsvc.yaml ``` Start `auto-scale` networkservicemesh endpoints: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-client?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-server?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-client?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-server?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Create kubernetes service for the networkservicemesh proxy-endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/client/dashboard.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/client/dashboard.yaml ``` Wait for the dashboard client to be ready @@ -87,7 +87,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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/server/counting_nsm.yaml ``` Wait for new counting pod to be ready: ```bash @@ -108,13 +108,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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/server/counting_nsm.yaml -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/client/dashboard.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-client?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-server?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/server/counting_service.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_consul/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/server/counting_nsm.yaml +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/client/dashboard.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-client?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_consul/nse-auto-scale-server?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/server/counting_service.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_consul/netsvc.yaml kubectl --kubeconfig=$KUBECONFIG2 delete pods --all ``` ```bash diff --git a/examples/interdomain/nsm_istio/README.md b/examples/interdomain/nsm_istio/README.md index 751573c14bd9..a8fcb8d29d8e 100644 --- a/examples/interdomain/nsm_istio/README.md +++ b/examples/interdomain/nsm_istio/README.md @@ -31,25 +31,25 @@ istioctl --kubeconfig=$KUBECONFIG2 proxy-status Install networkservice for the second cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_istio/greeting/client.yaml ``` Start `auto-scale` networkservicemesh endpoint: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_istio/nse-auto-scale?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_istio/nse-auto-scale?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio/greeting/server.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_istio/greeting/server.yaml ``` Wait for the `alpine` client to be ready: @@ -74,10 +74,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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio/greeting/server.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_istio/nse-auto-scale?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio/greeting/client.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_istio/greeting/server.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_istio/nse-auto-scale?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_istio/greeting/client.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/nsm_istio_booking/README.md b/examples/interdomain/nsm_istio_booking/README.md index 4f3d174eab1b..c4ea7d482e68 100644 --- a/examples/interdomain/nsm_istio_booking/README.md +++ b/examples/interdomain/nsm_istio_booking/README.md @@ -37,18 +37,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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio_booking/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/nsm_istio_booking/nse-auto-scale?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_istio_booking/nse-auto-scale?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Install istio booking example @@ -81,9 +81,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/nsm_istio_booking/nse-auto-scale?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d -kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio_booking/productpage/productpage.yaml -kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_istio_booking/netsvc.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_istio_booking/nse-auto-scale?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 +kubectl --kubeconfig=$KUBECONFIG1 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_istio_booking/productpage/productpage.yaml +kubectl --kubeconfig=$KUBECONFIG2 delete -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/nsm_kuma_universal_vl3/README.md b/examples/interdomain/nsm_kuma_universal_vl3/README.md index cb695cdaf282..83bc52447411 100644 --- a/examples/interdomain/nsm_kuma_universal_vl3/README.md +++ b/examples/interdomain/nsm_kuma_universal_vl3/README.md @@ -11,7 +11,7 @@ ## Run 1. Start vl3 ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_kuma_universal_vl3/vl3-dns?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/interdomain/nsm_kuma_universal_vl3/vl3-dns?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 kubectl --kubeconfig=$KUBECONFIG1 -n ns-dns-vl3 wait --for=condition=ready --timeout=5m pod -l app=vl3-ipam ``` @@ -31,7 +31,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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_kuma_universal_vl3/namespace.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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 @@ -47,7 +47,7 @@ resources: - control-plane.yaml patchesStrategicMerge: -- https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_kuma_universal_vl3/patch-control-plane.yaml +- https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/nsm_kuma_universal_vl3/patch-control-plane.yaml EOF ``` @@ -58,13 +58,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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_kuma_universal_vl3/demo-redis.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/nsm_kuma_universal_vl3/demo-app.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/interdomain/spiffe_federation/README.md b/examples/interdomain/spiffe_federation/README.md index 3e9c7d335517..b6589dfa0219 100644 --- a/examples/interdomain/spiffe_federation/README.md +++ b/examples/interdomain/spiffe_federation/README.md @@ -11,12 +11,12 @@ Once federation is bootstrapped, the trust bundle updates are fetched trough the Apply the ClusterSPIFFEID CR for the first cluster: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/spiffe_federation/cluster1-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/interdomain/spiffe_federation/cluster2-spiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/interdomain/spiffe_federation/cluster2-spiffeid-template.yaml ``` Get and store bundles for clusters: diff --git a/examples/ipsec_mechanism/README.md b/examples/ipsec_mechanism/README.md index 54e7e8d8d3cb..fa1511b0541a 100644 --- a/examples/ipsec_mechanism/README.md +++ b/examples/ipsec_mechanism/README.md @@ -20,7 +20,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ipsec_mechanism?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/k8s_monolith/external_nsc/README.md b/examples/k8s_monolith/external_nsc/README.md index 3f864c10dd6d..b415a7d6c479 100644 --- a/examples/k8s_monolith/external_nsc/README.md +++ b/examples/k8s_monolith/external_nsc/README.md @@ -22,7 +22,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 833619e1d4ba..e709a39fc573 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/apps/nsc-simple-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/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 82bce14657a5..bd5bd9d2b421 100644 --- a/examples/k8s_monolith/external_nsc/spiffe_federation/README.md +++ b/examples/k8s_monolith/external_nsc/spiffe_federation/README.md @@ -14,7 +14,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/k8s_monolith/external_nsc/spiffe_federation/clusterspiffeid-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 2efa6b2c683e..b42dbaf775e3 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/k8s_monolith/external_nse/README.md b/examples/k8s_monolith/external_nse/README.md index 7189a166f91e..c5aefdcfc412 100644 --- a/examples/k8s_monolith/external_nse/README.md +++ b/examples/k8s_monolith/external_nse/README.md @@ -22,7 +22,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/configuration/cluster?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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 e0bc8a5085e3..2199ccd89ee5 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/apps/nse-simple-vl3-docker/docker-compose.yaml -o docker-compose.yaml +curl https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/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 2e30bde6d4c9..34820e55c56e 100644 --- a/examples/k8s_monolith/external_nse/spiffe_federation/README.md +++ b/examples/k8s_monolith/external_nse/spiffe_federation/README.md @@ -14,7 +14,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/k8s_monolith/external_nse/spiffe_federation/clusterspiffeid-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 8f2302758137..92b95b9453b5 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/k8s_monolith/external_nse/usecases/Kernel2IP2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Ethernet2Kernel/README.md b/examples/memory/Kernel2Ethernet2Kernel/README.md index cbb44e88d004..5983609771ce 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Ethernet2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/memory/Kernel2Kernel/README.md b/examples/memory/Kernel2Kernel/README.md index a9c3274f4518..35ffefb434c7 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Kernel2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/memory/Memif2Memif/README.md b/examples/memory/Memif2Memif/README.md index 457cfb008504..d85fd2ba9223 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory/Memif2Memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/memory/README.md b/examples/memory/README.md index a510f7185b39..1fdac1ca50f7 100644 --- a/examples/memory/README.md +++ b/examples/memory/README.md @@ -17,7 +17,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/memory?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/multicluster/README.md b/examples/multicluster/README.md index 526e526059da..0c4cfe379469 100644 --- a/examples/multicluster/README.md +++ b/examples/multicluster/README.md @@ -40,7 +40,7 @@ Interdomain tests can be on two clusters, for thus tests scheme of request will Apply NSM resources for basic tests: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/clusters-configuration/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/clusters-configuration/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for nsmgr-proxy-service exposing: @@ -59,7 +59,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/multicluster/clusters-configuration/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/clusters-configuration/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for nsmgr-proxy-service exposing: @@ -78,7 +78,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/multicluster/clusters-configuration/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/clusters-configuration/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for nsmgr-proxy-service exposing: diff --git a/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/README.md b/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/README.md index ad0a677c7c35..27a0128c27ee 100644 --- a/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/README.md +++ b/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/README.md @@ -18,14 +18,14 @@ Make sure that you have completed steps from [interdomain](../../) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/multicluster/usecases/floating_Kernel2Ethernet2Kernel/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2Ethernet2Kernel/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/multicluster/usecases/floating_Kernel2IP2Kernel/README.md b/examples/multicluster/usecases/floating_Kernel2IP2Kernel/README.md index d1d47ef3ebb6..bb6e5344955f 100644 --- a/examples/multicluster/usecases/floating_Kernel2IP2Kernel/README.md +++ b/examples/multicluster/usecases/floating_Kernel2IP2Kernel/README.md @@ -21,14 +21,14 @@ Make sure that you have completed steps from [interdomain](../../) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2IP2Kernel/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2IP2Kernel/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2IP2Kernel/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2IP2Kernel/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/multicluster/usecases/floating_Kernel2IP2Kernel/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_Kernel2IP2Kernel/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/multicluster/usecases/floating_dns/README.md b/examples/multicluster/usecases/floating_dns/README.md index f94fafb0b202..210706ccbc3d 100644 --- a/examples/multicluster/usecases/floating_dns/README.md +++ b/examples/multicluster/usecases/floating_dns/README.md @@ -14,21 +14,21 @@ Make sure that you have completed steps from [multicluster](../../) Deploy NetworkService: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_dns/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_dns/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **2. Deploy endpoint on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_dns/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_dns/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **3. Deploy client on cluster1** Deploy client: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_dns/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_dns/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/multicluster/usecases/floating_nse_composition/README.md b/examples/multicluster/usecases/floating_nse_composition/README.md index 2fa707ea0909..8a50f4874674 100644 --- a/examples/multicluster/usecases/floating_nse_composition/README.md +++ b/examples/multicluster/usecases/floating_nse_composition/README.md @@ -28,14 +28,14 @@ Make sure that you have completed steps from [interdomain](../../) Deploy NS: ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_nse_composition/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_nse_composition/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **2. Deploy endpoints on cluster2** Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_nse_composition/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_nse_composition/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/multicluster/usecases/floating_nse_composition/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_nse_composition/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/multicluster/usecases/floating_vl3-basic/README.md b/examples/multicluster/usecases/floating_vl3-basic/README.md index 36e5f057267a..f0500a7cfcc9 100644 --- a/examples/multicluster/usecases/floating_vl3-basic/README.md +++ b/examples/multicluster/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/multicluster/usecases/floating_vl3-basic/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Deploy a vl3-NSE and a client on the cluster1: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Deploy a vl3-NSE and a client on the cluster2: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **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/multicluster/usecases/floating_vl3-basic/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-basic/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` diff --git a/examples/multicluster/usecases/floating_vl3-dns/README.md b/examples/multicluster/usecases/floating_vl3-dns/README.md index e14c5793cc3d..9eaebc760ba2 100644 --- a/examples/multicluster/usecases/floating_vl3-dns/README.md +++ b/examples/multicluster/usecases/floating_vl3-dns/README.md @@ -16,13 +16,13 @@ Make sure that you have completed steps from [multicluster](../../) 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/multicluster/usecases/floating_vl3-dns/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/multicluster/usecases/floating_vl3-dns/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` ```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/multicluster/usecases/floating_vl3-dns/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` ```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/multicluster/usecases/floating_vl3-dns/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 2. Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 3. Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-dns/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` diff --git a/examples/multicluster/usecases/floating_vl3-scale-from-zero/README.md b/examples/multicluster/usecases/floating_vl3-scale-from-zero/README.md index cd83c7a13983..991ec82ecd4c 100644 --- a/examples/multicluster/usecases/floating_vl3-scale-from-zero/README.md +++ b/examples/multicluster/usecases/floating_vl3-scale-from-zero/README.md @@ -20,17 +20,17 @@ Start **vl3 ipam** and register **vl3 network service** in the *floating domain* Note: *By default ipam prefix is `172.16.0.0/16` and client prefix len is `24`. We also have two vl3 nses in this example. So we expect to have two vl3 addresses: `172.16.0.0` and `172.16.1.0` that should be accessible by each client.* ```bash -kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Start **nse-supplier-k8s** and client in the *cluster1*. ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Start **nse-supplier-k8s** and client in the *cluster2*. ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **2. Wait for clients to be ready** @@ -74,15 +74,15 @@ kubectl --kubeconfig=$KUBECONFIG2 exec pods/alpine -n ns-floating-vl3-scale-from Cleanup floating domain: ```bash -kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster3?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Cleanup cluster2 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Cleanup cluster1 domain: ```bash -kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 delete -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/floating_vl3-scale-from-zero/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` diff --git a/examples/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/README.md b/examples/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/README.md index c8159bb2134b..e267e95e76f4 100644 --- a/examples/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/README.md +++ b/examples/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/README.md @@ -15,7 +15,7 @@ Make sure that you have completed steps from [interdomain](../../) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_Kernel2Ethernet2Kernel/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/multicluster/usecases/interdomain_Kernel2IP2Kernel/README.md b/examples/multicluster/usecases/interdomain_Kernel2IP2Kernel/README.md index 79772db9c0a2..67a0b7e744dc 100644 --- a/examples/multicluster/usecases/interdomain_Kernel2IP2Kernel/README.md +++ b/examples/multicluster/usecases/interdomain_Kernel2IP2Kernel/README.md @@ -15,7 +15,7 @@ Make sure that you have completed steps from [interdomain](../../) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_Kernel2IP2Kernel/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_Kernel2IP2Kernel/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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/multicluster/usecases/interdomain_Kernel2IP2Kernel/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_Kernel2IP2Kernel/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/multicluster/usecases/interdomain_dns/README.md b/examples/multicluster/usecases/interdomain_dns/README.md index a1922099aa21..086abc282b0a 100644 --- a/examples/multicluster/usecases/interdomain_dns/README.md +++ b/examples/multicluster/usecases/interdomain_dns/README.md @@ -13,14 +13,14 @@ Make sure that you have completed steps from [multicluster](../../) Deploy NSE: ```bash -kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_dns/cluster2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_dns/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` **2. Deploy client on cluster1** Deploy client: ```bash -kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_dns/cluster1?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multicluster/usecases/interdomain_dns/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/multiforwarder/README.md b/examples/multiforwarder/README.md index 2fd89f2230cd..e903d1aa8048 100644 --- a/examples/multiforwarder/README.md +++ b/examples/multiforwarder/README.md @@ -39,7 +39,7 @@ For the `worker` node: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/multiforwarder_vlantag/README.md b/examples/multiforwarder_vlantag/README.md index 8dd404f2cdfa..e25ff5e5c97c 100644 --- a/examples/multiforwarder_vlantag/README.md +++ b/examples/multiforwarder_vlantag/README.md @@ -40,7 +40,7 @@ For the `worker` node: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/multiforwarder?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/observability/jaeger-and-prometheus/README.md b/examples/observability/jaeger-and-prometheus/README.md index 8b172fece1dd..d7b964d2d487 100644 --- a/examples/observability/jaeger-and-prometheus/README.md +++ b/examples/observability/jaeger-and-prometheus/README.md @@ -6,7 +6,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger-and-prometheus?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for OpenTelemetry Collector POD status ready: @@ -16,7 +16,7 @@ kubectl wait -n observability --timeout=1m --for=condition=ready pod -l app=open Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger-and-prometheus/nsm-system?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger-and-prometheus/nsm-system?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: @@ -27,7 +27,7 @@ kubectl wait --for=condition=ready --timeout=1m pod ${WH} -n nsm-system Deploy NSC and NSE: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger-and-prometheus/example?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/observability/jaeger-and-prometheus/example?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/ovs/README.md b/examples/ovs/README.md index d7b8ca1df5f0..026fdda313aa 100644 --- a/examples/ovs/README.md +++ b/examples/ovs/README.md @@ -38,7 +38,7 @@ For the `worker` node: Apply NSM resources for basic tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ovs?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/ovs?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/README.md b/examples/pss/README.md index 47b76479a3a1..a094c1a6fecc 100644 --- a/examples/pss/README.md +++ b/examples/pss/README.md @@ -20,7 +20,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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/nsm-system?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for admission-webhook-k8s: diff --git a/examples/pss/use-cases/nginx/README.md b/examples/pss/use-cases/nginx/README.md index 5e3f5e6ff8c0..279531c8931f 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/pss/use-cases/nginx?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/remotevlan_ovs/README.md b/examples/remotevlan_ovs/README.md index 5ad5d516dae2..39a00cd2444e 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_ovs?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for NSE application: diff --git a/examples/remotevlan_vpp/README.md b/examples/remotevlan_vpp/README.md index 5bfe9927b7e0..51222181f1ce 100644 --- a/examples/remotevlan_vpp/README.md +++ b/examples/remotevlan_vpp/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_vpp?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/remotevlan_vpp?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for NSE application: diff --git a/examples/spire/cluster1/README.md b/examples/spire/cluster1/README.md index 437c94d1fdd6..e29e89e99eaa 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG1 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for PODs status ready: @@ -27,7 +27,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/spire/cluster1/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG1 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/spire/cluster1/clusterspiffeid-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster2/README.md b/examples/spire/cluster2/README.md index 41eba08de62c..18bb6ce3e986 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG2 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for PODs status ready: @@ -27,7 +27,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/spire/cluster2/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG2 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/spire/cluster2/clusterspiffeid-template.yaml ``` ## Cleanup diff --git a/examples/spire/cluster3/README.md b/examples/spire/cluster3/README.md index 9a8bccd107c7..e5fcd7479af1 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl --kubeconfig=$KUBECONFIG3 apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/cluster3?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for PODs status ready: @@ -27,7 +27,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/spire/cluster3/clusterspiffeid-template.yaml +kubectl --kubeconfig=$KUBECONFIG3 apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/spire/cluster3/clusterspiffeid-template.yaml ``` ## Cleanup diff --git a/examples/spire/single_cluster/README.md b/examples/spire/single_cluster/README.md index 33ac2f701e03..9e1d929692c1 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for PODs status ready: @@ -19,7 +19,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ## Cleanup diff --git a/examples/spire/single_cluster_csi/README.md b/examples/spire/single_cluster_csi/README.md index e35be0c1739e..a50871c819f2 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/spire/single_cluster_csi?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for PODs status ready: @@ -19,7 +19,7 @@ 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/spire/single_cluster/clusterspiffeid-template.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/spire/single_cluster/clusterspiffeid-template.yaml ``` ## Cleanup diff --git a/examples/sriov/README.md b/examples/sriov/README.md index ceb4ad42a48e..407d0636617b 100644 --- a/examples/sriov/README.md +++ b/examples/sriov/README.md @@ -33,7 +33,7 @@ For the `worker` node: Apply NSM resources for sriov tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` ## Cleanup diff --git a/examples/sriov_vlantag/README.md b/examples/sriov_vlantag/README.md index 847d46663d49..97e40c053369 100644 --- a/examples/sriov_vlantag/README.md +++ b/examples/sriov_vlantag/README.md @@ -33,7 +33,7 @@ For the `worker` node: Apply NSM resources for sriov tests: ```bash -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/sriov?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` ## Cleanup diff --git a/examples/use-cases/Kernel2Ethernet2Kernel/README.md b/examples/use-cases/Kernel2Ethernet2Kernel/README.md index eb1d2550e2b1..b4a93674e353 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop/README.md index cee3814097a6..028813acfbaf 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2Noop?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag/README.md index a352c6f17002..629ab26d24d0 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Kernel_Vfio2NoopVlanTag?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Ethernet2Memif/README.md b/examples/use-cases/Kernel2Ethernet2Memif/README.md index 01e2c6a5082f..e55bf7000099 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Ethernet2Memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Kernel/README.md b/examples/use-cases/Kernel2IP2Kernel/README.md index bd322949b1e7..0dca19c09ef7 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2IP2Memif/README.md b/examples/use-cases/Kernel2IP2Memif/README.md index 9895114f7481..90c795083dfa 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2IP2Memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel/README.md b/examples/use-cases/Kernel2Kernel/README.md index 3196a2a3e028..7fbc3674d840 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2KernelVLAN/README.md b/examples/use-cases/Kernel2KernelVLAN/README.md index 957e4550489a..56b55e975fc8 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2KernelVLAN?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md b/examples/use-cases/Kernel2Kernel_Vfio2Noop/README.md index c82299b72361..6cc805b2acd6 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2Noop?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md b/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag/README.md index 913550a5d8a3..89233ca9d06f 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Kernel_Vfio2NoopVlanTag?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2Memif/README.md b/examples/use-cases/Kernel2Memif/README.md index 8dd1aedcf3d4..6fad60bc5020 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2Memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanBreakout/README.md b/examples/use-cases/Kernel2RVlanBreakout/README.md index e84db253070e..c76229c17c07 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanBreakout?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanInternal/README.md b/examples/use-cases/Kernel2RVlanInternal/README.md index 3a49f4fc3364..e6e37233c745 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanInternal?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Kernel2RVlanMultiNS/README.md b/examples/use-cases/Kernel2RVlanMultiNS/README.md index a6bf5a1e7157..29f2e6c5fde8 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Deployment in second namespace: ```bash -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml -kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml -kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/use-cases/Kernel2RVlanMultiNS/ns-2/ns-kernel2vlan-multins-2.yaml +kubectl apply -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/use-cases/Kernel2RVlanMultiNS/ns-2/netsvc.yaml +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Kernel2RVlanMultiNS/ns-2?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Deploy the last client ```bash -kubectl apply -n nsm-system -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/use-cases/Kernel2RVlanMultiNS/client.yaml +kubectl apply -n nsm-system -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/use-cases/Kernel2RVlanMultiNS/client.yaml ``` Wait for applications ready: @@ -341,7 +341,7 @@ true Delete the last client: ```bash -kubectl delete --namespace=nsm-system -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/9ad5ecb5e754a665b3a199b726e452a24dacee5d/examples/use-cases/Kernel2RVlanMultiNS/client.yaml +kubectl delete --namespace=nsm-system -f https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/examples/use-cases/Kernel2RVlanMultiNS/client.yaml ``` Delete the test namespace: diff --git a/examples/use-cases/Memif2Ethernet2Kernel/README.md b/examples/use-cases/Memif2Ethernet2Kernel/README.md index 7e6f01eb1307..6329103284a9 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Ethernet2Memif/README.md b/examples/use-cases/Memif2Ethernet2Memif/README.md index 0d4a0f99808e..b61c58519990 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Ethernet2Memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Kernel/README.md b/examples/use-cases/Memif2IP2Kernel/README.md index dac205524749..380c864bc405 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2IP2Memif/README.md b/examples/use-cases/Memif2IP2Memif/README.md index e7679d18cb8a..fc266416c009 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2IP2Memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Kernel/README.md b/examples/use-cases/Memif2Kernel/README.md index 59f760b30ef7..8489c60f67ec 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Kernel?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Memif2Memif/README.md b/examples/use-cases/Memif2Memif/README.md index f60fa287184b..d2129722966d 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Memif2Memif?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/SmartVF2SmartVF/README.md b/examples/use-cases/SmartVF2SmartVF/README.md index b0bfd2950356..6e1c6a1fc5a2 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SmartVF2SmartVF?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2Noop/README.md b/examples/use-cases/SriovKernel2Noop/README.md index 09004bc0e782..0376a1719a7c 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop/ponger?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2Noop?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/SriovKernel2NoopVlanTag/README.md b/examples/use-cases/SriovKernel2NoopVlanTag/README.md index 04bcdc17b773..255374f38f0c 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag/ponger?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/SriovKernel2NoopVlanTag?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2Noop/README.md b/examples/use-cases/Vfio2Noop/README.md index f11ed8c4072b..ecd40fc4c5e4 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2Noop?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/examples/use-cases/Vfio2NoopVlanTag/README.md b/examples/use-cases/Vfio2NoopVlanTag/README.md index cb2eb47572db..f614e2b05c6a 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=9ad5ecb5e754a665b3a199b726e452a24dacee5d +kubectl apply -k https://github.com/networkservicemesh/deployments-k8s/examples/use-cases/Vfio2NoopVlanTag?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3 ``` Wait for applications ready: diff --git a/to-ref.sh b/to-ref.sh index 3a3caa0b50b1..2869b8403c66 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/9ad5ecb5e754a665b3a199b726e452a24dacee5d/\1')" +FILE_PATTERN="$(escape 'https://raw.githubusercontent.com/networkservicemesh/deployments-k8s/e8c513d2e502cf86ca13b99b4e592b4dfe705dc3/\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=9ad5ecb5e754a665b3a199b726e452a24dacee5d')" +DIR_PATTERN="$(escape 'https://github.com/networkservicemesh/deployments-k8s/\1?ref=e8c513d2e502cf86ca13b99b4e592b4dfe705dc3')" grep "$(pwd)" -rl examples/* | while IFS= read -r file; do root="$(get_root "$file")" sedi -E "s/${root//./\.}\/([^ ]*)/${DIR_PATTERN}/g" "${file}"