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
Copy file name to clipboardExpand all lines: articles/aks/howto-deploy-java-liberty-app.md
+18-21Lines changed: 18 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,21 +59,19 @@ The following steps guide you to create a Liberty runtime on AKS. After completi
59
59
1. Create a new resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, `ejb0913-java-liberty-project-rg`.
60
60
1. Select *East US* as **Region**.
61
61
62
-
Create environment variables in your shell for the resource group name for the cluster.
1. Select **Next**, enter the **AKS** pane. This pane allows you to selectan existing AKS cluster and Azure Container Registry (ACR), instead of causing the deployment to create a new one, if desired. This capability enables you to use the sidecar pattern, as shown in the [Azure architecture center](/azure/architecture/patterns/sidecar). You can also adjust the settings forthe size and number of the virtual machinesin the AKS node pool. For our purposes, just keep all the defaults on this pane.
79
77
@@ -118,12 +116,12 @@ If you navigated away from the **Deployment is in progress** page, the following
118
116
119
117
---
120
118
121
-
These values are used later in this article. Note that several other useful commands are listed in the outputs.
119
+
These values are used later in this article. Note that several other useful commands are listed in the outputs.
122
120
123
-
> [!NOTE]
124
-
> You may notice a similar output named **appDeploymentYaml**. The difference between output *appDeploymentTemplateYaml* and *appDeploymentYaml* is:
125
-
>**appDeploymentTemplateYaml* is populated if and only if the deployment **does not include** an application.
126
-
>**appDeploymentYaml* is populated if and only if the deployment **does include** an application.
121
+
> [!NOTE]
122
+
> You may notice a similar output named **appDeploymentYaml**. The difference between output *appDeploymentTemplateYaml* and *appDeploymentYaml* is:
123
+
>**appDeploymentTemplateYaml* is populated if and only if the deployment **does not include** an application.
124
+
>**appDeploymentYaml* is populated if and only if the deployment **does include** an application.
127
125
128
126
## Create an Azure SQL Database
129
127
@@ -213,7 +211,6 @@ Now that you gathered the necessary properties, you can build the application. T
213
211
214
212
#### [Bash](#tab/in-bash)
215
213
216
-
217
214
```bash
218
215
cd $BASE_DIR/java-app
219
216
# The following variables are used for deployment file generation into target.
0 commit comments