mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OCPBUGS-37863: Documented a private infra notice for ARO
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
1e655118dc
commit
8f552054d9
@@ -7,6 +7,12 @@
|
||||
= Optional: Preparing a private Microsoft Azure cluster for a private image registry
|
||||
|
||||
By installing a private image registry on a private Microsoft Azure cluster, you can create private storage endpoints. Private storage endpoints disable public facing endpoints to the registry's storage account, adding an extra layer of security to your {product-title} deployment.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
Do not install a private image registry on {azure-first} Red{nbsp}Hat OpenShift (ARO), because the endpoint can put your {azure-first} Red{nbsp}Hat OpenShift cluster in an unrecoverable state.
|
||||
====
|
||||
|
||||
Use the following guide to prepare your private Microsoft Azure cluster for installation with a private image registry.
|
||||
|
||||
.Prerequisites
|
||||
|
||||
@@ -8,6 +8,11 @@
|
||||
|
||||
You can leverage the Image Registry Operator to use private endpoints on Azure, which enables seamless configuration of private storage accounts when {product-title} is deployed on private Azure clusters. This allows you to deploy the image registry without exposing public-facing storage endpoints.
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
Do not configure a private storage endpoint on {azure-first} Red{nbsp}Hat OpenShift (ARO), because the endpoint can put your {azure-first} Red{nbsp}Hat OpenShift cluster in an unrecoverable state.
|
||||
====
|
||||
|
||||
You can configure the Image Registry Operator to use private storage endpoints on Azure in one of two ways:
|
||||
|
||||
* By configuring the Image Registry Operator to discover the VNet and subnet names
|
||||
|
||||
Reference in New Issue
Block a user