|
1 | 1 | ---
|
2 |
| -title: Containerize your Java applications for Azure Kubernetes Service |
3 |
| -description: This article describes how to containerize your Java applications on Azure Kubernetes Service |
| 2 | +title: Containerize your Java applications for Kubernetes |
| 3 | +description: This article describes how to containerize your Java applications for Kubernetes deployment |
4 | 4 | ms.author: brborges
|
5 | 5 | ms.topic: conceptual
|
6 | 6 | ms.date: 04/13/2022
|
7 | 7 | ms.custom: devx-track-java
|
8 | 8 | recommendations: false
|
9 | 9 | ---
|
10 | 10 |
|
11 |
| -# Containerize your Java applications for Azure Kubernetes Service |
| 11 | +# Containerize your Java applications for Kubernetes |
12 | 12 |
|
13 |
| -This article describes how to containerize your Java applications on Azure Kubernetes Services. |
| 13 | +This article describes how to containerize your Java applications for deployment on Kubernetes. |
14 | 14 |
|
15 | 15 | For guidance on container memory, JVM heap memory, garbage collectors (GCs), and vCPU cores, see [Containerize your Java applications](overview.md).
|
16 | 16 |
|
17 |
| -## Determine the appropriate VM SKU for the AKS node pool |
| 17 | +## Determine the appropriate VM SKU for the Kubernetes node pool |
18 | 18 |
|
19 |
| -Determine whether the Azure Kubernetes Service node pool or pools that are available for your cluster can fit the container memory and vCPU cores that you intend to use. If the AKS node pool can host the application, then continue on. Otherwise, provision a node pool that's appropriate for the amount of container memory and number of vCPU cores you're targeting. |
| 19 | +Determine whether the Kubernetes node pool or pools that are available for your cluster can fit the container memory and vCPU cores that you intend to use. If the node pool can host the application, then continue on. Otherwise, provision a node pool that's appropriate for the amount of container memory and number of vCPU cores you're targeting. |
20 | 20 |
|
21 | 21 | Keep in mind that the cost of a VM SKU is proportional to the number of cores and amount of memory. After you determine your starting point in terms of vCPUs and memory for one container instance, determine whether you can meet your application's needs by horizontal scaling only. For reliable, always-on systems, a minimum of two replicas must be available. Scale up and out as needed.
|
22 | 22 |
|
@@ -83,4 +83,4 @@ containers:
|
83 | 83 |
|
84 | 84 | ## Next steps
|
85 | 85 |
|
86 |
| -* [Java on Azure containerization documentation](index.yml) |
| 86 | +* [Java containerization strategies](index.yml) |
0 commit comments