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
- Ensure that you have performed software inventory by providing the server credentials on the appliance configuration manager. [Learn more](how-to-discover-applications.md).
49
-
- Only Migrate projects created with Public endpoint connectivity are supported. Private endpoint projects are not supported.
49
+
- Only Migrate projects created with Public endpoint connectivity are supported. Private endpoint projects aren't supported.
50
50
51
51
## Set up Kubernetes-based appliance
52
52
@@ -56,7 +56,7 @@ After you have performed server discovery and software inventory using the Azure
56
56
57
57
1. Go to the [Azure portal](https://aka.ms/migrate/springboot). Sign in with your Azure account and search for Azure Migrate.
58
58
2. On the **Overview** page > **Servers, databases and web apps**, select **Discover, assess and migrate**.
59
-
1. Select the project where you have set up the Azure Migrate appliance as part of the prerequisites.
59
+
1. Select the project where you set up the Azure Migrate appliance as part of the prerequisites.
60
60
1. You see a message above Azure Migrate: Discovery and assessment tile to onboard a Kubernetes-based appliance to enable discovery of Spring Boot applications.
61
61
62
62
:::image type="content" source="./media/tutorial-discover-spring-boot/discover-banner-inline.png" alt-text="Screenshot shows the banner for discovery and assessment of web apps." lightbox="./media/tutorial-discover-spring-boot/discover-banner-expanded.png":::
@@ -145,7 +145,7 @@ After you save the script on the Linux server, follow these steps:
145
145
146
146
> [!Note]
147
147
> This script needs to be run after you connect to a Linux machine on its terminal that has met the networking pre-requisite and OS compatibility.
148
-
> Ensure that you have curl installed on the server. For Ubuntu, you can install it using the command `sudo apt-get install curl`, and for other OS (RHEL/Centos), you can use the command `yum install curl`.
148
+
> Ensure that you have curl installed on the server. For Ubuntu, you can install it using the command `sudo apt-get install curl`, and for other OS (RHEL/CentOS), you can use the command `yum install curl`.
149
149
150
150
> [!Important]
151
151
> Don't edit the script unless you want to clean up the setup.
@@ -174,7 +174,7 @@ After you save the script on the Linux server, follow these steps:
174
174
175
175
> [!Note]
176
176
> - This script needs to be run after you connect to a Linux machine on its terminal that meets the networking prerequisites and OS compatibility.
177
-
> - Ensure that you have curl installed on the server. For Ubuntu, you can install it using the command `sudo apt-get install curl`, and for other OS (RHEL/Centos), you can use the `yum install curl` command.
177
+
> - Ensure that you have curl installed on the server. For Ubuntu, you can install it using the command `sudo apt-get install curl`, and for other OS (RHEL/CentOS), you can use the `yum install curl` command.
178
178
179
179
> [!Important]
180
180
> Don't edit the script unless you want to clean up the setup.
@@ -205,7 +205,7 @@ After you save the script on the Linux server, follow these steps:
205
205
206
206
#### [Packaged Kubernetes cluster](#tab/cluster)
207
207
208
-
As you are setting a packaged appliance, we would have shared responsibility to ensure that the secrets are secured.
208
+
As you're setting a packaged appliance, we have shared responsibility to ensure that the secrets are secured.
209
209
- We recommend you choose a Linux VM with disk encryption for its services.
210
210
211
211
#### [Bring your own Kubernetes cluster](#tab/encrypt-rest)
@@ -236,10 +236,10 @@ After successfully setting up the appliance using the installer script, you need
236
236
237
237
> [!Note]
238
238
> - The credentials added on the portal are processed via the Azure Key Vault chosen in the initial steps of onboarding the Kubernetes-based appliance. The credentials are then synced (saved in an encrypted format) to the Kubernetes cluster on the appliance and removed from the Azure Key Vault.
239
-
> - After the credentials have been successfully synced, they would be used for discovery of the specific workload in the next discovery cycle.
239
+
> - After the credentials are successfully synced, they would be used for discovery of the specific workload in the next discovery cycle.
240
240
241
241
7. After adding a credential, you need to refresh the page to see the **Sync status** of the credential. If status is **Incomplete**, you can select the status to review the error encountered and take the recommended action.
242
-
After the credentials have been successfully synced, wait for 24 hours before you can review the discovered inventory by filtering for the specific workload in the **Discovered servers** page.
242
+
After the credentials are successfully synced, wait for 24 hours before you can review the discovered inventory by filtering for the specific workload in the **Discovered servers** page.
243
243
244
244
> [!Note]
245
245
> You can add/update credentials any time by navigating to **Azure Migrate: Discovery and assessment** > **Overview** > **Manage** > **Appliances** page, selecting **Manage credentials** from the options available in the Kubernetes-based appliance.
@@ -248,7 +248,7 @@ After the credentials have been successfully synced, wait for 24 hours before yo
248
248
249
249
To cleanup, run the following script in delete mode:
250
250
251
-
In the script generated by the portal, after all the user arguments (after line 19 in the following image), add `export DELETE= “true”` and run the same script again. This will clean up all existing components created during appliance creation.
251
+
In the script generated by the portal, after all the user arguments (after line 19 in the following image), add `export DELETE= “true”` and run the same script again. This cleans up all existing components created during appliance creation.
0 commit comments