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
@@ -20,10 +20,15 @@ This article uses the Azure Marketplace offer for JBoss EAP to accelerate your j
20
20
21
21
- A Red Hat account with complete profile. If you don't have one, you can sign up for a free developer subscription through the [Red Hat Developer Subscription for Individuals](https://developers.redhat.com/register).
22
22
23
-
- A local developer command line with a UNIX command environment and Azure CLI installed. To learn how to install the Azure CLI, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
23
+
- A local developer command line with a UNIX-like command environment - for example, Ubuntu, macOS, or Windows Subsystem for Linux - and Azure CLI installed. To learn how to install the Azure CLI, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
24
24
25
-
- The `mysql` CLI. For instructions see [How To Install MySQL](https://www.digitalocean.com/community/tutorials/how-to-install-mysql-on-ubuntu-20-04).
25
+
- The `mysql` CLI. You can install the CLI by using the following commands:
26
26
27
+
```azurecli-interactive
28
+
sudo apt update
29
+
sudo apt install mysql-server
30
+
```
31
+
27
32
> [!NOTE]
28
33
> You can also execute this guidance from the [Azure Cloud Shell](/azure/cloud-shell/quickstart). This approach has all the prerequisite tools pre-installed.
29
34
>
@@ -88,7 +93,7 @@ Use the following steps to deploy a service principal and get its Application (c
88
93
1. Provide a description of the secret and a duration. When you're done, select **Add**.
89
94
1. After the client secret is added, the value of the client secret is displayed. Copy this value because you can't retrieve it later. Be sure to copy the **Value** and not the **Secret ID**.
90
95
91
-
You've created your Microsoft Entra application, service principal, and client secret.
96
+
You created your Microsoft Entra application, service principal, and client secret.
92
97
93
98
## Create a Red Hat Container Registry service account
94
99
@@ -106,7 +111,7 @@ Use the following steps to create a Red Hat Container Registry service account a
106
111
- Note down the **username**, including the prepended string (that is, `XXXXXXX|username`). Use this username when you sign in to `registry.redhat.io`.
107
112
- Note down the **password**. Use this password when you sign in to `registry.redhat.io`.
108
113
109
-
You've created your Red Hat Container Registry service account.
114
+
You created your Red Hat Container Registry service account.
110
115
111
116
## Deploy JBoss EAP on Azure Red Hat OpenShift
112
117
@@ -171,9 +176,9 @@ The following sections show you how to set up Azure Database for MySQL - Flexibl
171
176
172
177
### Set environment variables in the command line shell
173
178
174
-
The application is a Jakarta EE application backed by a MySQL database, and is deployed to the OpenShift cluster using Source-to-Image (S2I). For more information about S2I, see the [S2I Documentation](http://red.ht/eap-aro-s2i).
179
+
The sample is a Java application backed by a MySQL database, and is deployed to the OpenShift cluster using Source-to-Image (S2I). For more information about S2I, see the [S2I Documentation](http://red.ht/eap-aro-s2i).
175
180
176
-
Open a shell, or Cloud Shell, and set the following environment variables. Replace the substitutions as appropriate.
181
+
Open a shell and set the following environment variables. Replace the substitutions as appropriate.
177
182
178
183
```azurecli-interactive
179
184
RG_NAME=<resource-group-name>
@@ -198,7 +203,7 @@ Replace the placeholders with the following values, which are used throughout th
198
203
-`ADMIN_PASSWORD`: The admin password of your MySQL database server. This article was tested using the password shown. Consult the database documentation for password rules.
199
204
-`<red-hat-container-registry-service-account-username>` and `<red-hat-container-registry-service-account-password>`: The username and password of the Red Hat Container Registry service account you created before.
200
205
201
-
It's a good idea to save the fully filled out name/value pairs in a text file, in case the shell exits or the Azure Cloud Shell times out before you're done executing the commands. That way, you can paste them into a new instance of the shell or Cloud Shell and easily continue.
206
+
It's a good idea to save the fully filled out name/value pairs in a text file, in case the shell exits before you're done executing the commands. That way, you can paste them into a new instance of the shell and easily continue.
202
207
203
208
These name/value pairs are essentially "secrets." For a production-ready way to secure Azure Red Hat OpenShift, including secret management, see [Security for the Azure Red Hat OpenShift landing zone accelerator](/azure/cloud-adoption-framework/scenarios/app-platform/azure-red-hat-openshift/security).
204
209
@@ -301,7 +306,7 @@ If you navigated away from the **Deployment is in progress** page, the following
301
306
302
307
1. In the navigation pane, select **Outputs**. This list shows the output values from the deployment, which includes some useful information.
303
308
304
-
1. Open the shell or Azure Cloud Shell, paste the value from the **cmdToGetKubeadminCredentials** field, and execute it. You see the admin account and credential for signing in to the OpenShift cluster console portal. The following example shows an admin account:
309
+
1. Open the shell, paste the value from the **cmdToGetKubeadminCredentials** field, and execute it. You see the admin account and credential for signing in to the OpenShift cluster console portal. The following example shows an admin account:
305
310
306
311
```azurecli
307
312
az aro list-credentials --resource-group eaparo033123rg --name clusterf9e8b9
@@ -322,7 +327,7 @@ If you navigated away from the **Deployment is in progress** page, the following
322
327
323
328
Next, use the following steps to connect to the OpenShift cluster using the OpenShift CLI:
324
329
325
-
1. In the shell or Azure Cloud Shell, use the following commands to download the latest OpenShift 4 CLI for GNU/Linux. If running on an OS other than GNU/Linux, download the appropriate binary for that OS.
330
+
1. In the shell, use the following commands to download the latest OpenShift 4 CLI for GNU/Linux. If running on an OS other than GNU/Linux, download the appropriate binary for that OS.
326
331
327
332
```azurecli-interactive
328
333
cd ~
@@ -333,7 +338,7 @@ Next, use the following steps to connect to the OpenShift cluster using the Open
1. Paste the value from the **cmdToLoginWithKubeadmin** field into the shell or Azure Cloud Shell, and execute it. You should see the `login successful` message and the project you're using. The following content is an example of the command to connect to the OpenShift cluster using the OpenShift CLI.
341
+
1. Paste the value from the **cmdToLoginWithKubeadmin** field into the shell, and execute it. You should see the `login successful` message and the project you're using. The following content is an example of the command to connect to the OpenShift cluster using the OpenShift CLI.
337
342
338
343
```azurecli-interactive
339
344
oc login \
@@ -372,7 +377,7 @@ The steps in this section show you how to deploy an app on the cluster.
372
377
373
378
Use the following steps to deploy the app to the cluster. The app is hosted in the GitHub repo [rhel-jboss-templates/eap-coffee-app](https://github.com/Azure/rhel-jboss-templates/tree/main/eap-coffee-app).
374
379
375
-
1. In the shell or Azure Cloud Shell, run the following commands. The commands create a project, apply a permission to enable S2I to work, image the pull secret, and link the secret to the relative service accounts in the project to enable the image pull. Disregard the git warning about "'detached HEAD' state."
380
+
1. In the shell, run the following commands. The commands create a project, apply a permission to enable S2I to work, image the pull secret, and link the secret to the relative service accounts in the project to enable the image pull. Disregard the git warning about "'detached HEAD' state."
@@ -482,7 +487,7 @@ Next, use the following steps to create a secret:
482
487
EOF
483
488
```
484
489
485
-
If the command completed successfully, you should see `wildflyserver.wildfly.org/javaee-cafe created`. If you don't see this output, troubleshoot and resolve the problem before proceeding.
490
+
If the command completed successfully, you should see `wildflyserver.wildfly.org/javaee-cafe created`. If you don't see this output, troubleshoot and resolve the problem before proceeding.
486
491
487
492
1. Run `oc get pod -w | grep 1/1` to monitor whether all pods of the app are running. When you see output similar to the following example, press <kbd>Ctrl</kbd> + <kbd>C</kbd> to stop the monitoring:
0 commit comments