updating namespace in yaml examples

EricssonResearch · May 3, 2022 · 2b77f26 · 2b77f26
1 parent ed9ff7d
commit 2b77f26
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/generator/examples/simple/cluster1/service1.yaml b/generator/examples/simple/cluster1/service1.yaml
@@ -5,7 +5,7 @@ metadata:
     labels:
         name: config-service1
         version: cluster1
-    namespace: edge-namespace
+    namespace: default
 data:
     conf.json: '{"processes":2,"threads":2,"endpoints":[{"name":"endpoint1","protocol":"http","execution_mode":"sequential","network_complexity":{"forward_requests":"asynchronous","response_payload_size":512,"called_services":[{"service":"service2","port":"80","endpoint":"endpoint1","protocol":"http","traffic_forward_ratio":1,"request_payload_size":256},{"service":"service2","port":"80","endpoint":"endpoint2","protocol":"http","traffic_forward_ratio":1,"request_payload_size":256}]}},{"name":"endpoint2","protocol":"http","execution_mode":"parallel","network_complexity":{"forward_requests":"asynchronous","response_payload_size":512,"called_services":[]}}]}'
     service.proto: "syntax = \"proto3\";\n\n\nservice service1 {\n    \n    rpc endpoint1 (Request) returns (Response) {}\n    \n    rpc endpoint2 (Request) returns (Response) {}\n    \n}\n\nservice service2 {\n    \n    rpc endpoint1 (Request) returns (Response) {}\n    \n    rpc endpoint2 (Request) returns (Response) {}\n    \n}\n\n\nmessage Request {\n    string data = 1;\n}\n\nmessage Response {\n    string data = 1;\n}"
@@ -14,7 +14,7 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
     name: service1
-    namespace: edge-namespace
+    namespace: default
     labels:
         version: cluster1
 spec:
@@ -64,7 +64,7 @@ apiVersion: v1
 kind: Service
 metadata:
     name: service1
-    namespace: edge-namespace
+    namespace: default
     labels:
         version: cluster1
     annotations:

diff --git a/generator/examples/simple/cluster1/service2.yaml b/generator/examples/simple/cluster1/service2.yaml
@@ -5,7 +5,7 @@ metadata:
     labels:
         name: config-service2
         version: cluster1
-    namespace: edge-namespace
+    namespace: default
 data:
     conf.json: '{"processes":2,"threads":2,"endpoints":[{"name":"endpoint1","protocol":"http","execution_mode":"parallel","cpu_complexity":{"execution_time":"1s","method":"fibonacci","workers":2,"cpu_affinity":[1,2],"cpu_load":"10%"},"memory_complexity":{"execution_time":"1s","method":"swap","workers":24,"bytes_load":"10%"},"network_complexity":{"forward_requests":"asynchronous","response_payload_size":512,"called_services":[]}},{"name":"endpoint2","protocol":"http","execution_mode":"parallel","network_complexity":{"forward_requests":"asynchronous","response_payload_size":512,"called_services":[]}}]}'
     service.proto: "syntax = \"proto3\";\n\n\nservice service1 {\n    \n    rpc endpoint1 (Request) returns (Response) {}\n    \n    rpc endpoint2 (Request) returns (Response) {}\n    \n}\n\nservice service2 {\n    \n    rpc endpoint1 (Request) returns (Response) {}\n    \n    rpc endpoint2 (Request) returns (Response) {}\n    \n}\n\n\nmessage Request {\n    string data = 1;\n}\n\nmessage Response {\n    string data = 1;\n}"
@@ -14,7 +14,7 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
     name: service2
-    namespace: edge-namespace
+    namespace: default
     labels:
         version: cluster1
 spec:
@@ -64,7 +64,7 @@ apiVersion: v1
 kind: Service
 metadata:
     name: service2
-    namespace: edge-namespace
+    namespace: default
     labels:
         version: cluster1
     annotations: