In {product-title} {product-version}, you can install a cluster on bare metal infrastructure that you provision in a restricted network.
|
Important
|
While you might be able to follow this procedure to deploy a cluster on virtualized or cloud environments, you must be aware of additional considerations for non-bare metal platforms. Review the information in the guidelines for deploying {product-title} on non-tested platforms before you attempt to install an {product-title} cluster in such an environment. |
-
You reviewed details about the {product-title} installation and update processes.
-
You read the documentation on selecting a cluster installation method and preparing it for users.
-
You created a registry on your mirror host and obtained the
imageContentSourcesdata for your version of {product-title}.ImportantBecause the installation media is on the mirror host, you can use that computer to complete all installation steps.
-
You provisioned persistent storage for your cluster. To deploy a private image registry, your storage must provide ReadWriteMany access modes.
-
If you use a firewall and plan to use the Telemetry service, you configured the firewall to allow the sites that your cluster requires access to.
NoteBe sure to also review this site list if you are configuring a proxy.
For a cluster that contains user-provisioned infrastructure, you must deploy all of the required machines.
This section describes the requirements for deploying {product-title} on user-provisioned infrastructure.
modules/installation-machine-requirements.adoc modules/installation-minimum-resource-requirements.adoc
-
See Configuring a three-node cluster for details about deploying three-node clusters in bare metal environments.
-
See Approving the certificate signing requests for your machines for more information about approving cluster certificate signing requests after installation.
-
See Load balancing requirements for user-provisioned infrastructure for more information on the API and application ingress load balancing requirements.
-
See Recovering from expired control plane certificates for more information about recovering kubelet certificates.
modules/installation-user-infra-machines-advanced-customizing-live-iscsi-ibft.adoc :boot-media!: :boot!:
modules/installation-user-infra-machines-advanced-customizing-live-iscsi-ibft.adoc :boot-media!: :boot!:
-
See Monitoring installation progress for more information about monitoring the installation logs and retrieving diagnostic data if installation issues arise.
-
See Gathering logs from a failed installation for details about gathering data in the event of a failed {product-title} installation.
-
See Troubleshooting Operator issues for steps to check Operator pod health across the cluster and gather Operator logs for diagnosis.
-
See About remote health monitoring for more information about the Telemetry service
-
Configure image streams for the Cluster Samples Operator and the
must-gathertool. -
Learn how to use Operator Lifecycle Manager in disconnected environments.
-
If the mirror registry that you used to install your cluster has a trusted CA, add it to the cluster by configuring additional trust stores.
-
If necessary, you can opt out of remote health reporting.
-
If necessary, see Registering your disconnected cluster