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/ai-services/openai/includes/use-your-data-powershell.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,4 +80,4 @@ The available health plans in the Contoso Electronics plan and benefit packages
80
80
81
81
## Chat with your model using a web app
82
82
83
-
To start chatting with the Azure OpenAI model that uses your data, you can deploy a web app using [Azure OpenAI studio](../concepts/use-your-data.md#deploy-to-a-copilot-preview-teams-app-preview-or-web-app) or example code we [provide on GitHub](https://go.microsoft.com/fwlink/?linkid=2244395). This app deploys using Azure app service, and provides a user interface for sending queries. This app can be used Azure OpenAI models that use your data, or models that don't use your data. See the readme file in the repo for instructions on requirements, setup, and deployment. You can optionally customize the [frontend and backend logic](../how-to/use-web-app.md#web-app-customization) of the web app by making changes to the source code.
83
+
To start chatting with the Azure OpenAI model that uses your data, you can deploy a web app using [Azure OpenAI studio](../concepts/use-your-data.md#deploy-to-a-copilot-preview-teams-app-preview-or-web-app) or example code we [provide on GitHub](https://go.microsoft.com/fwlink/?linkid=2244395). This app deploys using Azure app service, and provides a user interface for sending queries. This app can be used with Azure OpenAI models that use your data, or models that don't use your data. See the readme file in the repo for instructions on requirements, setup, and deployment. You can optionally customize the [frontend and backend logic](../how-to/use-web-app.md#customizing-the-application-using-environment-variables) of the web app by making changes to the source code.
Copy file name to clipboardExpand all lines: articles/ai-services/openai/includes/use-your-data-rest.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,4 +90,4 @@ curl -i -X POST $AZURE_OPENAI_ENDPOINT/openai/deployments/$AZURE_OPENAI_DEPLOYME
90
90
91
91
## Chat with your model using a web app
92
92
93
-
To start chatting with the Azure OpenAI model that uses your data, you can deploy a web app using [Azure OpenAI studio](../concepts/use-your-data.md#deploy-to-a-copilot-preview-teams-app-preview-or-web-app) or example code we [provide on GitHub](https://go.microsoft.com/fwlink/?linkid=2244395). This app deploys using Azure app service, and provides a user interface for sending queries. This app can be used Azure OpenAI models that use your data, or models that don't use your data. See the readme file in the repo for instructions on requirements, setup, and deployment. You can optionally customize the [frontend and backend logic](../how-to/use-web-app.md#web-app-customization) of the web app by making changes to the source code.
93
+
To start chatting with the Azure OpenAI model that uses your data, you can deploy a web app using [Azure OpenAI studio](../concepts/use-your-data.md#deploy-to-a-copilot-preview-teams-app-preview-or-web-app) or example code we [provide on GitHub](https://go.microsoft.com/fwlink/?linkid=2244395). This app deploys using Azure app service, and provides a user interface for sending queries. This app can be used with Azure OpenAI models that use your data, or models that don't use your data. See the readme file in the repo for instructions on requirements, setup, and deployment. You can optionally customize the [frontend and backend logic](../how-to/use-web-app.md#customizing-the-application-using-environment-variables) of the web app by making changes to the source code.
@@ -91,7 +91,7 @@ This error occurs when the export policy isn't defined with a unique index. When
91
91
* Cause:
92
92
The defined export policy doesn't meet the requirement for export policy rules. You must have one export policy rule at the minimum and five export policy rules at the maximum.
93
93
* Solution:
94
-
Make sure that the index isn't already used and that it is in the range from 1 to 5.
94
+
Make sure that the index isn't already used and that it's in the range from 1 to 5.
95
95
* Workaround:
96
96
Use a different index for the rule that you're trying to set.
97
97
@@ -113,7 +113,7 @@ This error occurs when the file path contains unsupported characters, for exampl
113
113
* Cause:
114
114
The file path contains unsupported characters, for example, a period ("."), comma (","), underscore ("_"), or dollar sign ("$").
115
115
* Solution:
116
-
Remove characters that are not alphabetical letters, numbers, or hyphens ("-") from the file path you entered.
116
+
Remove all characters other than alphabetical letters, numbers, or hyphens ("-") from the file path you entered.
117
117
* Workaround:
118
118
You can replace an underscore with a hyphen or use capitalization instead of spaces to indicate the beginning of new words. For example, use "NewVolume" instead of "new volume".
119
119
@@ -261,7 +261,7 @@ Wait a few minutes and check if the problem persists.
261
261
262
262
***Not allowed to mix protocol types CIFS and NFS***
263
263
264
-
This error occurs when you're trying to create a Volume and there are both the CIFS (SMB) and NFS protocol types in the volume properties.
264
+
This error occurs when you're trying to create a volume that has both the CIFS (SMB) and NFS protocol types in the volume properties.
265
265
266
266
* Cause:
267
267
Both the CIFS (SMB) and NFS protocol types are used in the volume properties.
@@ -299,7 +299,7 @@ This error indicates that the operation isn't available for the active subscript
299
299
* Cause:
300
300
The operation isn't available for the subscription or resource.
301
301
* Solution:
302
-
Make sure that the operation is entered correctly and that it is available for the resource and subscription that you're using.
302
+
Make sure that the operation is entered correctly. The operation should be available for the resource and subscription that you're using.
303
303
304
304
***OwnerId cannot be changed***
305
305
@@ -317,14 +317,14 @@ This error occurs when you try to create a volume and the capacity pool in which
317
317
* Cause:
318
318
The capacity pool where the volume is being created isn't found.
319
319
* Solution:
320
-
Most likely the pool was not fully created or was already deleted at the time of the volume creation.
320
+
Most likely the pool wasn't fully created or was already deleted at the time of the volume creation.
321
321
322
322
***Patch operation is not supported for this resource type.***
323
323
324
324
This error occurs when you try to change the mount target or snapshot.
325
325
326
326
* Cause:
327
-
The mount target is defined when it is created, and it can't be changed subsequently.
327
+
The mount target is defined when it's created, and it can't be changed subsequently.
328
328
The snapshots don’t contain any properties that can be changed.
329
329
* Solution:
330
330
None. Those resources don't have any properties that can be changed.
@@ -407,7 +407,7 @@ This error occurs when you try to reference a nonexistent resource, for example,
407
407
* Cause:
408
408
You're trying to reference a nonexistent resource (for example, a volume or snapshot) that has already been deleted or has a misspelled resource name.
409
409
* Solution:
410
-
Check the request for spelling errors to make sure that it is correctly referenced.
410
+
Check the request for spelling errors to make sure that it's correctly referenced.
411
411
* Workaround:
412
412
See the Solution section above.
413
413
@@ -495,7 +495,7 @@ This error occurs when nonexistent properties are provided for a resource such a
495
495
* Cause:
496
496
The request has a set of properties that can be used with each resource. You can't include any nonexistent properties in the request.
497
497
* Solution:
498
-
Make sure that all property names are spelled correctly and that the properties are available for the subscription and resource.
498
+
Make sure all property names are spelled correctly. Make sure the properties are available for the subscription and resource.
499
499
* Workaround:
500
500
Reduce the number of properties defined in the request to eliminate the property that is causing the error.
501
501
@@ -534,7 +534,7 @@ See the solution above.
534
534
535
535
***Volume is being deleted and cannot be deleted at the moment.***
536
536
537
-
This error occurs when you try to delete a volume when it is already being deleted.
537
+
This error occurs when you try to delete a volume when it's already being deleted.
538
538
539
539
* Cause:
540
540
A volume is already being deleted when you try to delete the volume.
@@ -635,7 +635,7 @@ This error occurs when you try to create an SMB volume, but a DNS server (specif
635
635
* Cause:
636
636
You're trying to create an SMB volume, but a DNS server (specified in your Active Directory configuration) is unreachable.
637
637
* Solution:
638
-
Review your Active Directory configuration and make sure that the DNS server IP addresses are correct and reachable.
638
+
Review your Active Directory configuration. Make sure that the DNS server IP addresses are correct and reachable.
639
639
If there’s no issues with the DNS server IP addresses, then verify that no firewalls are blocking the access.
Copy file name to clipboardExpand all lines: articles/openshift/howto-multiple-ips.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Configure multiple IP addresses for ARO cluster load balancers (Preview)
2
+
title: Configure multiple IP addresses for ARO cluster load balancers
3
3
description: Discover how to configure multiple IP addresses for ARO cluster load balancers.
4
4
author: johnmarco
5
5
ms.author: johnmarc
@@ -8,12 +8,20 @@ ms.topic: how-to
8
8
ms.date: 03/05/2024
9
9
#Customer intent: As an ARO SRE, I need to configure multiple outbound IP addresses per ARO cluster load balancers
10
10
---
11
-
# Configure multiple IP addresses per ARO cluster load balancer (Preview)
11
+
# Configure multiple IP addresses per ARO cluster load balancer
12
12
13
-
ARO public clusters are created with a public load balancer that's used for outbound connectivity from inside the cluster. By default, one public IP address is configured on that public load balancer, and that limits the maximum node count of your cluster to 62. To be able to scale your cluster to the maximum supported number of nodes, you need to assign multiple additional public IP addresses to the load balancer.
13
+
ARO public clusters are created with a public load balancer that's used for outbound connectivity from inside the cluster. By default, one public IP address is configured on that public load balancer, and that limits the maximum node count of your cluster to 65. To be able to scale your cluster to the maximum supported number of 250 nodes, you need to assign multiple additional public IP addresses to the load balancer.
14
14
15
15
You can configure up to 20 IP addresses per cluster. The outbound rules and frontend IP configurations are adjusted to accommodate the number of IP addresses.
16
16
17
+
> [!CAUTION]
18
+
> Before deleting a large cluster, descale the cluster to 120 nodes or below.
19
+
>
20
+
21
+
> [!NOTE]
22
+
> The [API](/rest/api/openshift/open-shift-clusters/update?view=rest-openshift-2023-11-22&tabs=HTTP) method for using this feature is generally available. General availability for using the CLI for this feature is coming soon. The [preview version](#download-aro-extension-wheel-file-preview-only) of this feature can still be used through the CLI.
23
+
>
24
+
17
25
## Requirements
18
26
19
27
The multiple public IPs feature is only available on the current network architecture used by ARO; older clusters don't support this feature. If your cluster was created before OpenShift Container Platform (OCP) version 4.5, this feature isn't available even if you upgraded your OCP version since then.
Copy file name to clipboardExpand all lines: articles/openshift/openshift-faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ metadata:
6
6
ms.author: johnmarc
7
7
ms.service: azure-redhat-openshift
8
8
ms.topic: faq
9
-
ms.date: 06/04/2023
9
+
ms.date: 08/08/2024
10
10
title: Azure Red Hat OpenShift FAQ
11
11
summary: This article answers frequently asked questions (FAQs) about Microsoft Azure Red Hat OpenShift.
12
12
@@ -31,7 +31,7 @@ sections:
31
31
answer: |
32
32
The actual number of supported pods depends on an application’s memory, CPU, and storage requirements.
33
33
34
-
Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 60 compute node limit. These limits cap the maximum number of pods supported in a cluster to 250×60 = 15,000. For a private cluster without any public IPs (for example, created by using [User Defined Routing (UDR)](howto-create-private-cluster-4x.md#create-a-private-cluster-without-a-public-ip-address) and running version 4.11 or higher), the limits are 120 compute nodes and 30,000 pods.
34
+
Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 250 compute node limit. These limits cap the maximum number of pods supported in a cluster to 250×250 = 62,500. These limits are the same for clusters created using [User Defined Routing (UDR)](howto-create-private-cluster-4x.md#create-a-private-cluster-without-a-public-ip-address) and running version 4.11 or higher.
35
35
36
36
- question: Can a cluster have compute nodes across multiple Azure regions?
37
37
answer: No. All nodes in an Azure Red Hat OpenShift cluster must originate in the same Azure region.
Copy file name to clipboardExpand all lines: articles/openshift/support-policies-v4.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ Certain configurations for Azure Red Hat OpenShift 4 clusters can affect your cl
22
22
23
23
* The cluster must have a minimum of three worker nodes and three master nodes.
24
24
* Don't scale the cluster workers to zero, or attempt a cluster shutdown. Deallocating or powering down any virtual machine in the cluster resource group isn't supported.
25
+
* Don't create more than 250 worker nodes on a cluster. 250 is the maximum number of nodes that can be created on a cluster. See [Configure multiple IP addresses per ARO cluster load balancer](howto-multiple-ips.md) for more information.
25
26
* If you're making use of infrastructure nodes, don't run any undesignated workloads on them as this can affect the Service Level Agreement and cluster stability. Also, it's recommended to have three infrastructure nodes; one in each availability zone. See [Deploy infrastructure nodes in an Azure Red Hat OpenShift (ARO) cluster](howto-infrastructure-nodes.md) for more information.
26
27
* Non-RHCOS compute nodes aren't supported. For example, you can't use an RHEL compute node.
27
28
* Don't attempt to remove, replace, add, or modify a master node. That's a high risk operation that can cause issues with etcd, permanent network loss, and loss of access and manageability by ARO SRE. If you feel that a master node should be replaced or removed, contact support before making any changes.
0 commit comments