You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To run through the demo, refer to link:..//demo-script[Monitor the Mesh]
18
-
19
-
Like what you see, but can't quite put your finger on how you could use a Service Mesh? Check out link:../ideas-for-customization[Ways to customize the Mesh] for some ideas!
17
+
See link:../ideas-for-customization[Ways to customize the Mesh] for some ideas on how to customize the pattern.
Copy file name to clipboardExpand all lines: modules/trvlops-about.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Based on the requirements of a specific implementation, certain details might di
17
17
18
18
Background::
19
19
20
-
The {trvlops-pattern} deployed using OpenShift GitOps and is comprised of Red Hat Service Mesh (RHSM), Kiali for the Service Mesh console, Jaeger for distributed tracing, and elasticsearch for logging and analytics. The application deployed is from the Kiali traveldemo tutorial. This pattern isn't as much about the demo as it is about the capabilities that are enabled with a few simple configurations. Service Mesh's are being incorporated across multiple platforms to provide secure communications between services.
20
+
The {trvlops-pattern} deployed using OpenShift GitOps and is comprised of Red Hat Service Mesh (RHSM), Kiali for the Service Mesh console, Jaeger for distributed tracing, and elasticsearch for logging and analytics. The application deployed is from the link:https://kiali.io/docs/tutorials/travels/[Kiali traveldemo]. This pattern focuses on demonstrating capabilities enabled through simple configurations, rather than the demo itself. Service Mesh technology is adopted across multiple platforms to ensure secure communication between services.
21
21
22
22
//In this pattern we implement Mutual TLS (mTLS) which is completed per namespace. To enable a namespace in the mesh you must add the namespace to the list under `serviceMeshMemberNamespaces` in `values-travelops.yaml`. This will create a Service Mesh Member (SMM) resource, which tells the Service Mesh that resources in the namespace are authorized in the mesh.
** The cluster must have a dynamic `StorageClass` to provision `PersistentVolumes`. See link:../../multicloud-gitops/mcg-cluster-sizing[sizing your cluster].
11
+
** Select *OpenShift \-> Red Hat OpenShift Container Platform \-> Create cluster*.
12
+
** The cluster must have a dynamic `StorageClass` to provision `PersistentVolumes`. Verify that a dynamic `StorageClass` exists before creating one by running the following command:
13
+
+
14
+
[source,terminal]
15
+
----
16
+
$ oc get storageclass -o custom-columns=NAME:.metadata.name,PROVISIONER:.provisioner,DEFAULT:.metadata.annotations."storageclass\.kubernetes\.io/is-default-class"
17
+
----
18
+
+
19
+
.Example output
20
+
+
21
+
[source,terminal]
22
+
----
23
+
NAME PROVISIONER DEFAULT
24
+
gp2-csi ebs.csi.aws.com <none>
25
+
gp3-csi ebs.csi.aws.com true
26
+
----
27
+
+
28
+
For more information about creating a dynamic `StorageClass`, see the https://docs.openshift.com/container-platform/latest/storage/dynamic-provisioning.html[Dynamic provisioning] documentation.
29
+
13
30
* Optional: A second OpenShift cluster for multicloud demonstration.
14
31
//Replaced git and podman prereqs with the tooling dependencies page
15
32
* https://validatedpatterns.io/learn/quickstart/[Install the tooling dependencies].
@@ -22,22 +39,57 @@ public or private cloud by using https://console.redhat.com/openshift/create[Red
22
39
.Procedure
23
40
24
41
. Fork the https://github.com/validatedpatterns-sandbox/travelops[travelops] repository on GitHub.
# Ideally you NEVER COMMIT THESE VALUES TO GIT (although if all passwords are
43
95
# automatically generated inside the vault this should not really matter)
@@ -50,83 +102,92 @@ secrets:
50
102
- name: rootpasswd
51
103
onMissingValue: generate
52
104
vaultPolicy: validatedPatternDefaultPolicy
53
-
54
-
# Uncomment the following if you want to enable HTPasswd oAuth
55
-
# - name: htpasswd
56
-
# vaultPrefixes:
57
-
# - global
58
-
# fields:
59
-
# - name: htpasswd
60
-
# path: '/path/to/users.htpasswd'
61
105
----
62
106
+
63
107
[WARNING]
64
108
====
65
-
Do not commit this file. You do not want to push personal credentials to GitHub. If you do not want to customize the secrets, these steps are not needed. The framework generates a random password for the config-demo application.
109
+
Do not commit this file. Committing it may expose personal credentials to GitHub. If you do not want to customize the secrets, skip these steps. The framework generates a random password for the `config-demo` application.
66
110
====
67
111
68
-
. Customize the deployment for your cluster. Run the following command:
112
+
. Customize the deployment for your cluster by following these steps:
113
+
114
+
.. Create a new branch named my-branch and switch to it by running the following command:
69
115
+
70
116
[source,terminal]
71
117
----
72
-
git switch -c my-branch
118
+
$ git switch -c my-branch
73
119
----
120
+
121
+
.. Edit the `values-hub.yaml` file to customize the deployment for your cluster by running the following command:
74
122
+
75
123
[source,terminal]
76
124
----
77
-
vi values-hub.yaml
125
+
$ vi values-hub.yaml
78
126
----
127
+
128
+
.. Stage the changes to the `values-hub.yaml` file by running the following commands:
79
129
+
80
130
[source,terminal]
81
131
----
82
-
git add values-hub.yaml
132
+
$ git add values-hub.yaml
83
133
----
134
+
135
+
.. Commit the changes to the `values-hub.yaml` file by running the following commands:
84
136
+
85
137
[source,terminal]
86
138
----
87
-
git commit values-hub.yaml
139
+
$ git commit -m "update deployment for my-branch"
88
140
----
141
+
142
+
.. Push the changes to the `values-hub.yaml` file by running the following command:
89
143
+
90
144
[source,terminal]
91
145
----
92
-
git push origin my-branch
146
+
$ git push origin my-branch
93
147
----
94
148
95
149
. Deploy the pattern by running `./pattern.sh make install` or by using the link:/infrastructure/using-validated-pattern-operator/[Validated Patterns Operator].
96
150
97
151
[id="deploying-cluster-using-patternsh-file"]
98
-
== Deploying the cluster by using the pattern.sh file
152
+
== Deploying the pattern by using the pattern.sh script
99
153
100
-
To deploy the cluster by using the `pattern.sh` file, complete the following steps:
154
+
To deploy the pattern by using the `pattern.sh` script, complete the following steps:
101
155
102
-
. Login to your cluster by running the following command:
156
+
. Log in to your cluster by running the following:
157
+
158
+
.. Obtain an API token by visiting https://oauth-openshift.apps.<your-cluster>.<domain>/oauth/token/request
159
+
160
+
.. Log in with this retrieved token by running the following command:
Optional: Set the `KUBECONFIG` variable for the `kubeconfig` file path:
166
+
167
+
. Alternatively log in by running the following command:
110
168
+
111
169
[source,terminal]
112
170
----
113
-
export KUBECONFIG=~/<path_to_kubeconfig>
171
+
$ export KUBECONFIG=~/<path_to_kubeconfig>
114
172
----
115
173
116
-
. Deploy the pattern to your cluster. Run the following command:
174
+
. Deploy the pattern to your cluster by running the following command:
117
175
+
118
176
[source,terminal]
119
177
----
120
-
./pattern.sh make install
178
+
$ ./pattern.sh make install
121
179
----
122
180
123
181
[id="verify-trvlops-pattern-install"]
124
182
== Verify TravelOps Pattern installation
125
183
126
184
. Verify that the Operators have been installed.
185
+
127
186
.. To verify, in the OpenShift Container Platform web console, navigate to *Operators → Installed Operators* page.
128
-
.. Set your project to `All Projects` and verify the operators are isntalled and have a status of `Succeeded`.
129
-
. Verify that all applications are synchronized. Under the project `travelops-hub` click the URL for the `hub` gitops `server`.
187
+
188
+
.. Set your project to `All Projects` and verify the operators are installed and have a status of `Succeeded`.
189
+
190
+
. Verify that all applications are synchronized. Under *Networking* -> *Routes* with the project set to *travelops-hub* select the *Location URL* associated with the *hub-gitops-server* . All application are report status as `Synched`.
In the Kiali dashboard we can see how all of the various components interact with each other within the service mesh. Just to get a glimpse of what we are able to see let's take a look at the applications and services in the `travel-agency` namespace.
239
+
In the Kiali dashboard you can see how all of the various components interact with each other within the service mesh. Just to get a glimpse of what we are able to see let's take a look at the applications and services in the `travel-agency` namespace.
168
240
169
241
In the left hand menu:
170
242
171
-
* click Graph
172
-
* in the `Namespace` dropdown, select `travel-agency`
173
-
* exit the menu
243
+
. Cilck *Graph*.
174
244
175
-
You should see all of the deployments and services that make up the travel-agency application.
245
+
. In the `Namespace` dropdown, select `travel-agency`.
176
246
247
+
. Exit the menu
248
+
249
+
You should see all of the deployments and services that make up the travel-agency application.
0 commit comments