Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Actualize interdomain examples with latest changes in interdomain #2277

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions apps/nsmgr-proxy/nsmgr-proxy.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,10 @@ spec:
env:
- name: NSM_OUTPUTPATH
value: "/etc/mapip/config.yaml"
- name: NSM_NODENAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
volumeMounts:
- name: mapip-volume
mountPath: /etc/mapip
Expand Down
2 changes: 1 addition & 1 deletion apps/registry-memory/registry-memory.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ spec:
- name: REGISTRY_MEMORY_LISTEN_ON
value: tcp://:5002
- name: REGISTRY_MEMORY_PROXY_REGISTRY_URL
value: registry-proxy-svc:5003
value: nsmgr-proxy:5004
imagePullPolicy: IfNotPresent
name: registry
ports:
Expand Down
31 changes: 31 additions & 0 deletions examples/floating/dns/service.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
apiVersion: v1
kind: Service
metadata:
name: kube-dns
namespace: kube-system
annotations:
prometheus.io/port: "9153"
prometheus.io/scrape: "true"
labels:
k8s-app: kube-dns
kubernetes.io/cluster-service: "true"
kubernetes.io/name: "CoreDNS"
spec:
type: NodePort
selector:
k8s-app: kube-dns
clusterIP: 10.96.0.10
ports:
- name: dns
port: 53
nodePort: 30053
protocol: UDP
- name: dns-tcp
port: 53
nodePort: 30053
protocol: TCP
- name: metrics
port: 9153
protocol: TCP
nodePort: 30153
35 changes: 20 additions & 15 deletions examples/floating/usecases/Kernel2Vxlan2Kernel/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ kind: Kustomization
namespace: ${NAMESPACE1}

bases:
- ../../../apps/nse-kernel
- ../../../../apps/nse-kernel

patchesStrategicMerge:
- patch-nse.yaml
Expand All @@ -60,16 +60,21 @@ metadata:
name: nse-kernel
spec:
template:
metadata:
annotations:
registration-name: icmp-server@my.cluster3
spec:
containers:
- name: nse
env:
- name: NSM_CIDR_PREFIX
value: 172.16.1.2/31
- name: NSM_SERVICE_NAMES
value: icmp-responder@my.cluster3
- name: NSM_NAME
value: icmp-server@my.cluster3
- name: NSM_NAME
valueFrom:
fieldRef:
fieldPath: metadata.annotations['registration-name']
- name: NSM_CIDR_PREFIX
value: 172.16.1.2/31
- name: NSM_SERVICE_NAMES
value: icmp-responder@my.cluster3
EOF
```

Expand Down Expand Up @@ -117,7 +122,7 @@ kind: Kustomization
namespace: ${NAMESPACE2}

bases:
- ../../../apps/nsc-kernel
- ../../../../apps/nsc-kernel

patchesStrategicMerge:
- patch-nsc.yaml
Expand Down Expand Up @@ -185,18 +190,18 @@ kubectl exec ${NSE} -n ${NAMESPACE1} -- ping -c 4 172.16.1.3

## Cleanup

1. Cleanup resources for *cluster1*:
1. Cleanup resources for *cluster2*:
```bash
export KUBECONFIG=$KUBECONFIG1
export KUBECONFIG=$KUBECONFIG2
```
```bash
kubectl delete ns ${NAMESPACE2}
kubectl delete ns ${NAMESPACE1}
```

2. Cleanup resources for *cluster2*:
2. Cleanup resources for *cluster1*:
```bash
export KUBECONFIG=$KUBECONFIG2
export KUBECONFIG=$KUBECONFIG1
```
```bash
kubectl delete ns ${NAMESPACE1}
```
kubectl delete ns ${NAMESPACE2}
```
5 changes: 5 additions & 0 deletions examples/interdomain/basic/README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,10 @@
# Basic interdomain examples

The NSM interdomain functionality provides the ability for clients in one domain to connect to endpoints in another domain. Each domain has its own installation of NSM and domain specific configuration such that all the NSM control-planes are able to communicate with the NSM components required for connection setup.


![NSM interdomain Scheme](./interdomain_concept.png "NSM interdomain Scheme")


## Requires

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.