anchor.diff:  xref:../machine_management/creating_machinesets/creating-machineset-gcp.adoc#creating-machineset-gcp[GCP]
   by xref:../machine_management/deploying-machine-health-checks.adoc#deploying-machine-health-checks[deploying health checks] and xref:../machine_management/applying-autoscaling.adoc#applying-autoscaling[applying autoscaling to machines].
   
  -- **xref:../registry/registry-options.adoc#registry-options[Manage container registries]**: Each {product-title} cluster includes a built-in container registry for storing its images. You can also configure a separate link:https://access.redhat.com/documentation/en-us/red_hat_quay/[Red Hat Quay] registry to use with {product-title}. The link:https://quay.io[Quay.io] site provides a public container registry that stores {product-title} containers and Operators.
  +- **xref:../registry/registry-options.adoc#registry-options[Manage container registries]**: Each {product-title} cluster includes a built-in container registry for storing its images. You can also configure a separate link:https://access.redhat.com/documentation/en-us/red_hat_quay/[Red Hat Quay] registry to use with {product-title}. The link:https://quay.io[Quay.io] web site provides a public container registry that stores {product-title} containers and Operators.
   
   - **xref:../authentication/understanding-authentication.adoc#understanding-authentication[Manage users and groups]**: Add users and groups that have different levels of permissions to use or modify clusters.
   
  
positive.code: xref:../installing/install_config/installing-restricted-networks-preparations.adoc#installing-restricted-networks-preparations[mirror the {product-title} installation images]
  and install a cluster in a restricted network.
  
  - **Install a cluster in an existing network**: If you use an existing VPC in
  xref:../installing/installing_aws/installing-aws-vpc.adoc#installing-aws-vpc[AWS] or
  xref:../installing/installing_gcp/installing-gcp-vpc.adoc#installing-gcp-vpc[GCP] or an existing
  xref:../installing/installing_azure/installing-azure-vnet.adoc#installing-azure-vnet[VNet]
  on Azure, you can install a cluster 
  
  - **Install a private cluster**: If your cluster does not require external
  internet access, you can install a private cluster on
  xref:../installing/installing_aws/installing-aws-private.adoc#installing-aws-private[AWS],
  xref:../installing/installing_azure/installing-azure-private.adoc#installing-aws-private[Azure], or
  xref:../installing/installing_gcp/installing-gcp-private.adoc#installing-gcp-private[GCP].
  You still require internet access to access the cloud APIs and installation
  media.
  
  - **xref:../installing/installing-gather-logs.adoc#installing-gather-logs[Check installation logs]**: Access installation logs to evaluate issues that occur during {product-title} {product-version} installation.
  
  
negative.code: easily and automates deployment, build, and service route configurations.
  It abstracts complex Kubernetes and {product-title} concepts, allowing developers to focus on developing their applications.
  
  - **Deploy Helm Charts**:
  xref:../cli_reference/helm-cli/getting-started-with-helm-on-openshift-container-platform.adoc#getting-started-with-helm-on-openshift[Helm 3]
  is a package manager that helps developers define, install, and update
  application packages on Kubernetes. A Helm Chart is a packaging format that
  describes an application that can be deployed using the Helm CLI.
  
  - **xref:../operators/olm-what-operators-are.adoc#olm-what-operators-are[Understand Operators]**: Operators are the preferred method for creating on-cluster applications for {product-title} {product-version}. Learn about the Operator Framework and how to deploy applications using installed Operators into your projects.
  
  