-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathvalues-mesh-1.yaml
88 lines (77 loc) · 3.61 KB
/
values-mesh-1.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
# This Helm values are for your 1st OpenShift Service Mesh. Adjust the values according
# to you own environment. REMEMBER to also update the values for 2nd OpenShift Service
# Mesh in the values-mesh-2.yaml file.
#
# Notes:
#
# 1. Since the service mesh will dynamically generate other K8S objects based
# on your mesh name, and such name will be prefixed with some strings which
# cannot exceed certain amount of characters. Thus, suggest NOT to have a
# mesh name more than 8 characters.
#
# 2. You may change mesh version to a newer version if available and if compatible.
local-mesh-name: ossm1
local-mesh-version: v2.2
local-mesh-ctl-plane-namespace: peter-ossm1-ctl
local-mesh-bookinfo-namespace: peter-ossm1-app
remote-mesh-name: ossm2
remote-mesh-ctl-plane-namespace: peter-ossm2-ctl
remote-mesh-bookinfo-namespace: peter-ossm2-app
# Type 1:
# Enable the followings if you intent to use ClusterIP (usually both meshes are in
# the same OpenShift cluster) for federation gateway exposure. Comment out the
# followings if you DO NOT use ClusterIP.
#
# Notes:
#
# 1. If you are installion both service meshes within the same OpenShift, please
# ensure that the local mesh namespaces (both control plane and bookinfo) and remote
# mesh namespaces are NOT the same.
#
# 2. The value local-and-remote-connectivity-method must be the same across
# values-mesh-1.yaml and values-mesh-2.yaml. (In reality, you could have one end
# using one type, the other end using another type. However, to make the demo
# easier, we assume both ends are using the same type.)
local-and-remote-connectivity-method: ClusterIP
# Type 2:
# Enable the followings if you intent to use Load Balancer (usually for 2 clusters on
# public clouds) for federation gateway exposure. Comment out the followings if
# you DO NOT use Load Balancer.
#
# Notes:
#
# 1. The value local-and-remote-connectivity-method must be the same across
# values-mesh-1.yaml and values-mesh-2.yaml. (In reality, you could have one end
# using one type, the other end using another type. However, to make the demo
# easier, we assume both ends are using the same type.)
#
# 2. local-mesh-openshift-cloud-provider values could be: {AWS, Azure}
# local-and-remote-connectivity-method: LoadBalancer
# local-mesh-openshift-cloud-provider: Azure
# Type 3:
# Enable the followings if you intent to use NodePort (usually on-premises
# environment) for federation gateway exposure. Comment out the followings
# if you DO NOT use NodePort.
#
# Notes:
#
# 1. If you use NodePort, the peering addresses might be your worker node IP or FQDN.
# Make sure there are no firewall rules that block the port access.
#
# 2. For NodePort numbers, be aware that you must pick a port number which is above 30000
# and cannot be in used.
#
# 3. remote-mesh.peering-addresses is an array list. You may list all the IP
# addresses or FQDN of your worker nodes which has nodeport exposed.
#
# 4. The value local-and-remote-connectivity-method must be the same across
# values-mesh-1.yaml and values-mesh-2.yaml. (In reality, you could have one end
# using one type, the other end using another type. However, to make the demo
# easier, we assume both ends are using the same type.)
# local-and-remote-connectivity-method: NodePort
# local-mesh-ingress-gateway-nodeport-tls-port-number: 30443
# local-mesh-ingress-gateway-nodeport-https-discovery-port-number: 30188
# remote-mesh-ingress-gateway-nodeport-tls-port-number: 30443
# remote-mesh-ingress-gateway-nodeport-https-discovery-port-number: 30188
# remote-mesh-peering-addresses:
# - 192.168.1.112