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
@@ -166,8 +166,8 @@ So no worries, make your config repo public and proceed! You may need to also re
166
166
167
167
In case you are using a codespace for running this lab, your environment variables will be lost if the codespace restarts. For persisting these environment variables, you can either use the [guidance that GitHub provides for this](https://docs.github.com/en/enterprise-cloud@latest/codespaces/developing-in-codespaces/persisting-environment-variables-and-temporary-files). We recommend the [single workspace](https://docs.github.com/en/enterprise-cloud@latest/codespaces/developing-in-codespaces/persisting-environment-variables-and-temporary-files#for-a-single-codespace) approach, since that is the easiest to set up and doesn't require workspace restart.
168
168
169
-
You can find a [samplebashrc file](https://github.com/Azure-Samples/java-microservices-aks-lab/blob/main/solution/samplebashrc) in this repository. You will need to update a couple of values in this file for your specific situation.
169
+
You can find a [samplebashrc file](https://github.com/Azure-Samples/java-microservices-aca-lab/blob/main/solution/samplebashrc) in this repository. You will need to update a couple of values in this file for your specific situation.
170
170
171
171
Another approach would be to create a dedicated _.azcli_ file where you keep all environment variables. After a workspace restart, you first rerun all the steps in this file and you are good to go again.
172
172
173
-
You can find a [sampleENVIRONMENT.azcli file](https://github.com/Azure-Samples/java-microservices-aks-lab/blob/main/solution/sampleENVIRONMENT.azcli) in this repository. You will need to update a couple of values in this file for your specific situation.
173
+
You can find a [sampleENVIRONMENT.azcli file](https://github.com/Azure-Samples/java-microservices-aca-lab/blob/main/solution/sampleENVIRONMENT.azcli) in this repository. You will need to update a couple of values in this file for your specific situation.
Copy file name to clipboardExpand all lines: _config.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ title: Java microservices on ACA
2
2
description: This lab walks you through the creation of a Java microservices application on Azure Container Apps integrated with multiple Azure services
Copy file name to clipboardExpand all lines: config/README.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,4 +4,4 @@
4
4
5
5
Configuration repository for distributed Spring Petclinic application
6
6
7
-
This folder for the config repository is a close copy of the [spring-petclinic-microservices-config](https://github.com/spring-petclinic/spring-petclinic-microservices-config) repository and is used in the [Java microservices on AKS](https://azure-samples.github.io/java-microservices-aks-lab/) lab.
7
+
This folder for the config repository is a close copy of the [spring-petclinic-microservices-config](https://github.com/spring-petclinic/spring-petclinic-microservices-config) repository and is used in the [Java microservices on AKS](https://azure-samples.github.io/java-microservices-aca-lab/) lab.
The Spring Petclinic microservices provides a config server that your apps can use. You do need to however provide a git repository for this config server and link this git repo to the server. The current configuration used by the Spring microservices resides in the [config folder of the GitHub repo for this lab](https://github.com/Azure-Samples/java-microservices-aks-lab/tree/main/config). You will need to create your own private git repo in this exercise, since, in one of its steps, you will be changing some of the configuration settings.
10
+
The Spring Petclinic microservices provides a config server that your apps can use. You do need to however provide a git repository for this config server and link this git repo to the server. The current configuration used by the Spring microservices resides in the [config folder of the GitHub repo for this lab](https://github.com/Azure-Samples/java-microservices-aca-lab/tree/main/config). You will need to create your own private git repo in this exercise, since, in one of its steps, you will be changing some of the configuration settings.
11
11
12
12
{: .note }
13
13
> We simplified some of the original config of the spring-petclinic-microservices application to make some of the lab steps easier to execute.
@@ -58,17 +58,17 @@ Once you have your own config repository to work with, you will have to update t
58
58
{: .note }
59
59
> Make sure to replace the `<token>` and `<your-github-username>` placeholders in the URL listed above with the value of the GitHub PAT and your GitHub user name when running the `git clone` command.
60
60
61
-
1. From the Git Bash prompt, change the current directory to the newly created **spring-petclinic-microservices-config** folder and run the following commands to copy all the config server configuration yaml files from the [config folder of the GitHub repo for this lab](https://github.com/Azure-Samples/java-microservices-aks-lab/tree/main/config) to the local folder on your lab computer.
61
+
1. From the Git Bash prompt, change the current directory to the newly created **spring-petclinic-microservices-config** folder and run the following commands to copy all the config server configuration yaml files from the [config folder of the GitHub repo for this lab](https://github.com/Azure-Samples/java-microservices-aca-lab/tree/main/config) to the local folder on your lab computer.
1. From the Git Bash prompt, run the following commands to commit and push your changes to your private GitHub repository.
@@ -81,7 +81,7 @@ Once you have your own config repository to work with, you will have to update t
81
81
82
82
1. In your web browser, refresh the page of the newly created _spring-petclinic-microservices-config_ repository and double check that all the configuration files are there.
83
83
84
-
1. To configure the _spring-petclinic-config-server_ microservice so it points to your GitHub repository, in your _java-microservices-aks-lab_ project navigate to the _spring-petclinic-config-server/src/main/resources/application.yml_ file and update the uri of the git repo to use your own git repo uri. Also add 2 additional settings for your PAT username and password.
84
+
1. To configure the _spring-petclinic-config-server_ microservice so it points to your GitHub repository, in your _java-microservices-aca-lab_ project navigate to the _spring-petclinic-config-server/src/main/resources/application.yml_ file and update the uri of the git repo to use your own git repo uri. Also add 2 additional settings for your PAT username and password.
As a next step you will need to containerize your different microservice applications. You can do so by using the below starter for containerizing a spring boot application.
11
11
12
-
-[Configure settings for the Spring Cloud Config Server component in Azure Container Apps](https://github.com/Azure-Samples/java-microservices-aks-lab/compare/main...vermegi:java-microservices-aks-lab:upstream/solution-aca-demo)
13
-
-[Connect to a managed Spring Cloud Eureka Server in Azure Container Apps](https://learn.microsoft.com/en-us/azure/container-apps/spring-cloud-eureka-server)
12
+
-[Configure settings for the Config Server for Spring component in Azure Container Apps (preview)](https://learn.microsoft.com/azure/container-apps/java-config-server-usage)
13
+
-[Tutorial: Connect to a managed Config Server for Spring in Azure Container Apps (preview)](https://learn.microsoft.com/azure/container-apps/java-config-server)
14
+
-[Configure settings for the Eureka Server for Spring component in Azure Container Apps (preview)](https://learn.microsoft.com/azure/container-apps/java-eureka-server-usage)
15
+
-[Tutorial: Connect to a managed Eureka Server for Spring in Azure Container Apps (preview)](https://learn.microsoft.com/azure/container-apps/spring-cloud-eureka-server)
Now that you have deployed each of the microservices, you will test them out to see if they were deployed correctly. Also inspect wether all pods are properly up and running. In case they are not, inspect the logs to figure out what might be missing.
11
11
12
-
-[Get public endpoints](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough#test-the-application)
12
+
-[Get public endpoints (THIS LINK IS NOT CORRECT!!!)](https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough#test-the-application)
Copy file name to clipboardExpand all lines: index.md
+5-7Lines changed: 5 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -4,24 +4,22 @@ layout: home
4
4
nav_order: 1
5
5
---
6
6
7
-
# Lab: Deploying and running Java Applications in Azure Kubernetes
7
+
# Lab: Deploying and running Java Applications in Azure Container Apps
8
8
9
-
This lab teaches you how to deploy the [Spring Petclinic Microservices](https://github.com/Azure-Samples/java-microservices-aks-lab/tree/main/src) application to an AKS cluster and integrate it with additional Azure services.
9
+
This lab teaches you how to deploy the [Spring Petclinic Microservices](https://github.com/Azure-Samples/java-microservices-aca-lab/tree/main/src) application to an Container Apps environment and integrate it with additional Azure services.
10
10
11
11
## Modules
12
12
13
13
This lab has modules on:
14
14
15
-
* Plan a Java application migration to Azure Kubernetes Service
16
-
* Migrate a Spring Apps microservices application to Azure Kubernetes Service
15
+
* Plan a Java application migration to Azure Container Apps Service
16
+
* Migrate a Spring Apps microservices application to Azure Container Apps Service
17
17
* Enable monitoring and end-to-end tracing
18
18
* Secure application secrets using Key Vault
19
-
* Create and configure Azure Service Bus for sending messages between microservices
20
-
* Create and configure Azure Event Hubs for sending events between microservices
21
19
* Protect endpoints using Web Application Firewalls
22
20
* Secure MySQL database and Key Vault using a Private Endpoint
23
21
24
-
The lab is available as GitHub pages [here](https://azure-samples.github.io/java-microservices-aks-lab/)
22
+
The lab is available as GitHub pages [here](https://azure-samples.github.io/java-microservices-aca-lab/)
Copy file name to clipboardExpand all lines: install.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@ For running this lab with all the needed tooling, there are 3 options available:
17
17
18
18
## Using a GitHub Codespace
19
19
20
-
The [git repository of this lab](https://github.com/Azure-Samples/java-microservices-aks-lab) contains a dev container for Java development. This container contains all the needed tools for running this lab. In case you want to use this dev container you can use a [GitHub CodeSpace](https://github.com/features/codespaces) in case your GitHub account is enabled for Codespaces.
20
+
The [git repository of this lab](https://github.com/Azure-Samples/java-microservices-aca-lab) contains a dev container for Java development. This container contains all the needed tools for running this lab. In case you want to use this dev container you can use a [GitHub CodeSpace](https://github.com/features/codespaces) in case your GitHub account is enabled for Codespaces.
21
21
22
-
1. Navigate to the [GitHub repository of this lab](https://github.com/Azure-Samples/java-microservices-aks-lab) and select **Fork**.
22
+
1. Navigate to the [GitHub repository of this lab](https://github.com/Azure-Samples/java-microservices-aca-lab) and select **Fork**.
23
23
24
24
{: .note }
25
25
> In case you are using a GitHub EMU account, it might be you are not able to fork a public repository. In that case, create a new repository with the same name, clone the original repository, add your new repository as a remote and push to this new remote.
@@ -38,7 +38,7 @@ The [git repository of this lab](https://github.com/Azure-Samples/java-microserv
38
38
39
39
## Using Visual Studio Code with remote containers
40
40
41
-
The [git repository of this lab](https://github.com/Azure-Samples/java-microservices-aks-lab) contains a dev container for Java development. This container contains all the needed tools for running this lab. For this option you need the following tools to be installed on your local system:
41
+
The [git repository of this lab](https://github.com/Azure-Samples/java-microservices-aca-lab) contains a dev container for Java development. This container contains all the needed tools for running this lab. For this option you need the following tools to be installed on your local system:
42
42
43
43
- Visual Studio Code available from [Visual Studio Code Downloads](https://code.visualstudio.com/download)
44
44
- Git for Windows 2.3.61 available from [Git Downloads](https://git-scm.com/downloads), or similar on another OS.
1. When prompted to sign in to GitHub, select the **Sign in with your browser** option. This will automatically open a new tab in the web browser window, prompting you to provide your GitHub username and password.
@@ -81,10 +81,10 @@ To get started follow the below step by step instructions:
81
81
{: .note }
82
82
> However in one of the lab steps you will put a GitHub PAT token in one of the configuration files, make sure to **not** commit this PAT token, since it will immediately get invalidated by GitHub. Once invalidated your next lab steps will fail. You can use the [LabTips]({% link LabTips.md %}) to recover from this.
83
83
84
-
1. Navigate into the `java-microservices-aks-lab/src` folder that got created.
84
+
1. Navigate into the `java-microservices-aca-lab/src` folder that got created.
Once all these tools are installed, to get started you need to:
144
144
145
-
1. Navigate to the [GitHub repository of this lab](https://github.com/Azure-Samples/java-microservices-aks-lab) and select **Fork**.
145
+
1. Navigate to the [GitHub repository of this lab](https://github.com/Azure-Samples/java-microservices-aca-lab) and select **Fork**.
146
146
147
147
{: .note }
148
148
> In case you are using a GitHub EMU account, it might be you are not able to fork a public repository. In that case, create a new repository with the same name, clone the original repository, add your new repository as a remote and push to this new remote.
@@ -156,7 +156,7 @@ Once all these tools are installed, to get started you need to:
1. When prompted to sign in to GitHub, select the **Sign in with your browser** option. This will automatically open a new tab in the web browser window, prompting you to provide your GitHub username and password.
@@ -165,10 +165,10 @@ Once all these tools are installed, to get started you need to:
165
165
166
166
1. In workspaces folder double check that the spring petclinic application got cloned correctly. You can use the repository in your workspaces folder to regularly push your changes to.
167
167
168
-
1. Navigate into the _java-microservices-aks-lab/src_ folder that got created.
168
+
1. Navigate into the _java-microservices-aca-lab/src_ folder that got created.
0 commit comments