Merge pull request #276812 from backwind1233/s2i_aro_autodeploy

Auto Redeploy JBoss EAP on Azure Red Hat OpenShift With Source-2-Image (S2I)

Author: JamesJBarnett

articles/openshift/howto-deploy-java-jboss-enterprise-application-platform-app.md

@@ -67,7 +67,7 @@ The Azure Marketplace offer you're going to use in this article requires a Micro
 Use the following steps to deploy a service principal and get its Application (client) ID and secret from the Azure portal. For more information, see [Create and use a service principal to deploy an Azure Red Hat OpenShift cluster](/azure/openshift/howto-create-service-principal?pivots=aro-azureportal).
 
 > [!NOTE]
-> You must have sufficient permissions to register an application with your Microsoft Entra tenant. If you run into a problem, check the required permissions to make sure your account can create the identity. For more information, see the [Permissions required for registering an app](/azure/active-directory/develop/howto-create-service-principal-portal#permissions-required-for-registering-an-app) section of [Use the portal to create a Microsoft Entra application and service principal that can access resources](/azure/active-directory/develop/howto-create-service-principal-portal).
+> You must have sufficient permissions to register an application with your Microsoft Entra tenant. If you run into a problem, check the required permissions to make sure your account can create the identity. For more information, see [Register a Microsoft Entra app and create a service principal](/entra/identity-platform/howto-create-service-principal-portal).
 
 1. Sign in to your Azure account through the [Azure portal](https://portal.azure.com/).
 1. Select **Microsoft Entra ID**.

articles/openshift/howto-deploy-java-jboss-enterprise-application-platform-with-auto-redeploy.md

@@ -0,0 +1,10 @@
+---
+author: backwind1233
+ms.author: zhihaoguo
+ms.date: 06/26/2024
+ms.topic: include
+---
+
+## Clean up resources
+
+If you're not going to continue to use the OpenShift cluster, navigate back to your working resource group. At the top of the page, under the text **Resource group**, select the resource group. Then, select **Delete resource group**.

articles/openshift/howto-deploy-java-liberty-app.md

@@ -0,0 +1,30 @@
+---
+author: backwind1233
+ms.author: zhihaoguo
+ms.date: 06/26/2024
+ms.topic: include
+---
+
+## Get a Red Hat pull secret
+
+The Azure Marketplace offer used in this article requires a Red Hat pull secret. This section shows you how to get a Red Hat pull secret for Azure Red Hat OpenShift. To learn about what a Red Hat pull secret is and why you need it, see the [Get a Red Hat pull secret](../tutorial-create-cluster.md#get-a-red-hat-pull-secret-optional) section of [Tutorial: Create an Azure Red Hat OpenShift 4 cluster](../tutorial-create-cluster.md).
+
+Use the following steps to get the pull secret:
+
+1. Open the [Red Hat OpenShift Hybrid Cloud Console](https://console.redhat.com/openshift/install/azure/aro-provisioned), then use your Red Hat account to sign in to the OpenShift cluster manager portal. You may need to accept more terms and update your account as shown in the following screenshot. Use the same password as when you created the account.
+
+   :::image type="content" source="../media/howto-deploy-java-jboss-enterprise-application-platform-app/red-hat-account-complete-profile.png" alt-text="Screenshot of Red Hat Update Your Account page." lightbox="../media/howto-deploy-java-jboss-enterprise-application-platform-app/red-hat-account-complete-profile.png":::
+
+1. After you sign in, select **OpenShift** then **Downloads**.
+1. Select the **All categories** dropdown list and then select **Tokens**.
+1. Under **Pull secret**, select **Copy** or **Download** to get the value, as shown in the following screenshot.
+
+   :::image type="content" source="../media/howto-deploy-java-jboss-enterprise-application-platform-app/red-hat-console-portal-pull-secret.png" alt-text="Screenshot of the Red Hat console portal that shows the pull secret." lightbox="../media/howto-deploy-java-jboss-enterprise-application-platform-app/red-hat-console-portal-pull-secret.png":::
+
+   The following content is an example that was copied from the Red Hat console portal, with the auth codes replaced with `xxxx...xxx`.
+
+   ```json
+   {"auths":{"cloud.openshift.com":{"auth":"xxxx...xxx","email":"[email protected]"},"quay.io":{"auth":"xxx...xxx","email":"[email protected]"},"registry.connect.redhat.com":{"auth":"xxxx...xxx","email":"[email protected]"},"registry.redhat.io":{"auth":"xxxx...xxx","email":"[email protected]"}}}
+   ```
+
+1. Save the secret to a file so you can use it later.

articles/openshift/includes/jboss-eap-aro-cleanup.md

@@ -0,0 +1,9 @@
+---
+author: backwind1233
+ms.author: zhihaoguo
+ms.date: 06/26/2024
+ms.topic: include
+---
+
+> [!NOTE]
+> Azure Red Hat OpenShift requires a minimum of 40 cores to create and run an OpenShift cluster. The default Azure resource quota for a new Azure subscription doesn't meet this requirement. To request an increase in your resource limit, see [Increase VM-family vCPU quotas](../../quotas/per-vm-quota-requests.md). Note that the free trial subscription isn't eligible for a quota increase. Upgrade to a Pay-As-You-Go subscription before you request a quota increase. For more information, see [Upgrade your Azure free account or Azure for Students Starter account](../../cost-management-billing/manage/upgrade-azure-subscription.md).

articles/openshift/includes/jboss-eap-aro-get-pullsecret.md

@@ -0,0 +1,10 @@
+---
+author: backwind1233
+ms.author: zhihaoguo
+ms.date: 06/26/2024
+ms.topic: include
+---
+
+## Next step
+
+For more information about deploying JBoss EAP on Azure, see [Red Hat JBoss EAP on Azure](/azure/developer/java/ee/jboss-on-azure?toc=/azure/openshift/toc.json&bc=/azure/openshift/breadcrumb/toc.json).

articles/openshift/includes/jboss-eap-aro-minimum-cores.md

@@ -0,0 +1,24 @@
+---
+author: backwind1233
+ms.author: zhihaoguo
+ms.date: 06/26/2024
+ms.topic: include
+---
+
+## Create a Red Hat Container Registry service account
+
+Later, this article shows you how to manually deploy an application to OpenShift using Source-to-Image (S2I). A Red Hat Container Registry service account is necessary to pull the container image for JBoss EAP on which to run your application. If you have a Red Hat Container Registry service account ready to use, skip this section and move on to the next section, where you deploy the offer.
+
+Use the following steps to create a Red Hat Container Registry service account and get its username and password. For more information, see [Creating Registry Service Accounts](https://access.redhat.com/RegistryAuthentication#creating-registry-service-accounts-6) in the Red Hat documentation.
+
+1. Use your Red Hat account to sign in to the [Registry Service Account Management Application](https://access.redhat.com/terms-based-registry/).
+1. From the **Registry Service Accounts** page, select **New Service Account**.
+1. Provide a name for the Service Account. The name is prepended with a fixed, random string.
+   - Enter a description.
+   - Select **create**.
+1. Navigate back to your Service Accounts.
+1. Select the Service Account you created.
+   - Note down the **username**, including the prepended string (that is, `XXXXXXX|username`). Use this username when you sign in to `registry.redhat.io`.
+   - Note down the **password**. Use this password when you sign in to `registry.redhat.io`.
+
+You created your Red Hat Container Registry service account.

articles/openshift/includes/jboss-eap-aro-next-step.md

@@ -0,0 +1,21 @@
+---
+author: backwind1233
+ms.author: zhihaoguo
+ms.date: 06/26/2024
+ms.topic: include
+---
+
+### Validate the service principal
+
+Use the following command to validate the service principal:
+
+```azurecli
+az login \
+    --service-principal \
+    --username <service-principal-client-id> \
+    --password <service-principal-client-secret> \
+    --tenant <tenant-id>
+az account show
+```
+
+Replace `<service-principal-client-id>`, `<service-principal-client-secret>`, and `<tenant-id>` with the values you obtained in the previous steps. If you see the account information, the service principal is valid.