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/container-apps/faq.yml
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ sections:
43
43
- question: |
44
44
How is Azure Container Apps billed?
45
45
answer: |
46
-
Billing is based on resource consumption, including CPU, memory, and request count. For more information, refer to the [billing](billing.md) page.
46
+
Billing is based on resource consumption, including CPU, memory, and request count. For more information, see the [billing](billing.md) page.
47
47
48
48
- name: Configuration
49
49
questions:
@@ -83,7 +83,7 @@ sections:
83
83
answer: |
84
84
[Request a quota increase in the Azure portal](https://learn.microsoft.com/azure/quotas/quickstart-increase-quota-portal) with **Azure Container Apps** selected as the provider.
85
85
86
-
Consider the following when submitting a quota increase request:
86
+
Consider the following details when submitting a quota increase request:
87
87
88
88
- **Scaling apps vs environments**: There are many different quotas available to increase. Use these descriptions to help identify your needs:
89
89
- **Increase apps and cores per environment**: Allows you to run more apps within an environment and/or more intensive apps. Recommended if your workloads can deploy within the same network and security boundaries.
@@ -134,7 +134,7 @@ sections:
134
134
answer:
135
135
Custom version selection is **not supported**. Instead, your environment is automatically upgraded, maintaining the integrity of Dapr's fully managed and serverless offering in Azure Container Apps.
136
136
137
-
You can control auto-upgrades by [configuring the planned maintenance feature on your container apps environment](./planned-maintenance.md).
137
+
You can control autoupgrades by [configuring the planned maintenance feature on your container apps environment](./planned-maintenance.md).
138
138
139
139
- name: Dockerless deployments
140
140
questions:
@@ -145,7 +145,7 @@ sections:
145
145
- question: |
146
146
During the deployment of my Docker-less application, messages about "ImagePullBackOff on legion", "Kubernetes error" or "Gateway error" appear and my application doesn't deploy successfully.
147
147
answer: |
148
-
You're experiencing a known issue with Docker-less deployments. Retrying might resolve this for you. If you run into this issue, open a [GitHub issue](https://github.com/microsoft/azure-container-apps/issues) so our team can investigate.
148
+
You're experiencing a known issue with Docker-less deployments. Retrying might resolve this issue for you. If you run into this issue, open a [GitHub issue](https://github.com/microsoft/azure-container-apps/issues) so our team can investigate.
149
149
150
150
- name: Deploy .NET applications
151
151
questions:
@@ -159,7 +159,7 @@ sections:
159
159
- question: |
160
160
Which JDK versions are supported and how can I configure the JDK version?
161
161
answer: |
162
-
Container Apps supports four LTS JDK versions: JDK 8, JDK 11, JDK 17 and JDK 21.
162
+
Container Apps supports four LTS JDK versions: JDK 8, JDK 11, JDK 17, and JDK 21.
163
163
For source code build, the default version is JDK 17.
164
164
For a JAR file build, the JDK version is read from the file location *META-INF\MANIFEST.MF* in the JAR, but uses the default JDK version 17 if the specified version isn't available.
0 commit comments