forked from MicrosoftDocs/azure-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #200025 from TimShererWithAquent/t581147y
Edits to improve SEO and usability
- Loading branch information
Showing
1 changed file
with
15 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,27 +1,28 @@ | ||
| --- | ||
| title: Create a private cluster with Azure Red Hat OpenShift 3.11 | Microsoft Docs | ||
| description: Create a private cluster with Azure Red Hat OpenShift 3.11 | ||
| title: Create a private cluster with Azure Red Hat OpenShift 3.11 | ||
| description: Learn how to create a private cluster with Azure Red Hat OpenShift 3.11 and about the benefits of private clusters. | ||
| author: sakthi-vetrivel | ||
| ms.author: suvetriv | ||
| ms.service: azure-redhat-openshift | ||
| ms.topic: conceptual | ||
| ms.date: 03/02/2020 | ||
| ms.topic: how-to | ||
| ms.date: 06/02/2022 | ||
| ms.custom: kr2b-contr-experiment | ||
| keywords: aro, openshift, private cluster, red hat | ||
| #Customer intent: As a customer, I want to create a private cluster on ARO OpenShift. | ||
| --- | ||
|
|
||
| # Create a private cluster with Azure Red Hat OpenShift 3.11 | ||
|
|
||
| > [!IMPORTANT] | ||
| > Azure Red Hat OpenShift 3.11 will be retired 30 June 2022. Support for creation of new Azure Red Hat OpenShift 3.11 clusters continues through 30 November 2020. Following retirement, remaining Azure Red Hat OpenShift 3.11 clusters will be shut down to prevent security vulnerabilities. | ||
| > | ||
| > Azure Red Hat OpenShift 3.11 will be retired. Following retirement, remaining Azure Red Hat OpenShift 3.11 clusters will be shut down to prevent security vulnerabilities. | ||
| > | ||
| > Follow this guide to [create an Azure Red Hat OpenShift 4 cluster](tutorial-create-cluster.md). | ||
| > If you have specific questions, [please contact us](mailto:[email protected]). | ||
| > If you have specific questions, [contact us](mailto:[email protected]). | ||
| Private clusters provide the following benefits: | ||
|
|
||
| * Private clusters don't expose cluster control plane components (such as the API servers) on a public IP address. | ||
| * The virtual network of a private cluster is configurable by customers, allowing you to set up networking to allow peering with other virtual networks, including ExpressRoute environments. You can also configure custom DNS on the virtual network to integrate with internal services. | ||
| * Private clusters don't expose cluster control plane components, such as the API servers, on a public IP address. | ||
| * The virtual network of a private cluster is configurable by customers. You can set up networking to allow peering with other virtual networks, including ExpressRoute environments. You can also configure custom DNS on the virtual network to integrate with internal services. | ||
|
|
||
| ## Before you begin | ||
|
|
||
|
|
@@ -36,11 +37,11 @@ properties: | |
| privateApiServer: true | ||
| ``` | ||
|
|
||
| A private cluster can be deployed using the sample scripts provided below. Once the cluster is deployed, execute the `cluster get` command and view the `properties.FQDN` property to determine the private IP address of the OpenShift API server. | ||
| A private cluster can be deployed using the sample scripts provided below. Once the cluster is deployed, run the `cluster get` command and view the `properties.FQDN` property to determine the private IP address of the OpenShift API server. | ||
|
|
||
| The cluster virtual network will have been created with permissions so that you can modify it. You can then set up networking to access the virtual network (ExpressRoute, VPN, virtual network peering) as required for your needs. | ||
| The cluster virtual network is created with permissions so that you can modify it. You can set up networking to access the virtual network, such as ExpressRoute, VPN, and virtual network peering. | ||
|
|
||
| If you change the DNS nameservers on the cluster virtual network, then you will need to issue an update on the cluster with the `properties.RefreshCluster` property set to `true` so that the VMs can be reimaged. This update will allow them to pick up the new nameservers. | ||
| If you change the DNS nameservers on the cluster virtual network, issue an update on the cluster with the `properties.RefreshCluster` property set to `true` so that the virtual machines can be reimaged. This update allows them to pick up the new nameservers. | ||
|
|
||
| ## Sample configuration scripts | ||
|
|
||
|
|
@@ -51,7 +52,7 @@ Use the sample scripts in this section to set up and deploy your private cluster | |
| Fill in the environment variables below as using your own values. | ||
|
|
||
| > [!NOTE] | ||
| > The location must be set to `eastus2` as this is currently the only supported location for private clusters. | ||
| > The location must be set to `eastus2` because this is currently the only supported location for private clusters. | ||
| ``` bash | ||
| export CLUSTER_NAME= | ||
|
|
@@ -66,7 +67,7 @@ export SECRET= | |
|
|
||
| ### private-cluster.json | ||
|
|
||
| Using the environment variables defined above, here is a sample cluster configuration with private cluster enabled. | ||
| This sample is a cluster configuration with private cluster enabled. It uses the environment variables defined above. | ||
|
|
||
| ```json | ||
| { | ||
|
|
||