In {product-title} version {product-version}, you can install a cluster on {rh-openstack-first} that runs on user-provisioned infrastructure.
Using your own infrastructure allows you to integrate your cluster with existing infrastructure and modifications. The process requires more labor on your part than installer-provisioned installations, because you must create all {rh-openstack} resources, like Nova servers, Neutron ports, and security groups. However, Red Hat provides Ansible playbooks to help you in the deployment process.
-
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 verified that {product-title} {product-version} is compatible with your {rh-openstack} version by using the Supported platforms for OpenShift clusters section. You can also compare platform support across different versions by viewing the {product-title} on {rh-openstack} support matrix.
-
You have an {rh-openstack} account where you want to install {product-title}.
-
You understand performance and scalability practices for cluster scaling, control plane sizing, and etcd. For more information, see Recommended practices for scaling the cluster.
-
On the machine from which you run the installation program, you have:
-
A single directory in which you can keep the files you create during the installation process
-
Python 3
-
modules/cluster-entitlements.adoc modules/installation-osp-default-deployment.adoc modules/installation-osp-control-compute-machines.adoc modules/installation-osp-bootstrap-machine.adoc modules/installation-osp-downloading-modules.adoc modules/installation-osp-downloading-playbooks.adoc modules/installation-obtaining-installer.adoc modules/ssh-agent-using.adoc modules/installation-osp-creating-image.adoc modules/installation-osp-verifying-external-network.adoc modules/installation-osp-accessing-api.adoc modules/installation-osp-accessing-api-floating.adoc modules/installation-osp-accessing-api-no-floating.adoc modules/installation-osp-describing-cloud-parameters.adoc modules/installation-osp-creating-network-resources.adoc modules/installation-initializing.adoc
modules/installation-osp-custom-subnet.adoc modules/installation-osp-config-yaml.adoc modules/installation-osp-fixing-subnet.adoc modules/installation-osp-emptying-worker-pools.adoc modules/installation-osp-provider-networks.adoc modules/installation-osp-provider-network-preparation.adoc modules/installation-osp-deploying-provider-networks-installer.adoc
|
Tip
|
You can add additional networks, including provider networks, to the After you deploy your cluster, you can attach pods to additional networks. For more information, see Understanding multiple networks. |
modules/installation-user-infra-generate-k8s-manifest-ignition.adoc modules/installation-osp-converting-ignition-resources.adoc modules/installation-osp-creating-control-plane-ignition.adoc modules/installation-osp-updating-network-resources.adoc
modules/installation-osp-creating-bootstrap-machine.adoc modules/installation-osp-creating-control-plane.adoc modules/cli-logging-in-kubeadmin.adoc modules/installation-osp-deleting-bootstrap-resources.adoc modules/installation-osp-creating-compute-machines.adoc modules/installation-approve-csrs.adoc modules/installation-osp-verifying-installation.adoc
-
See About remote health monitoring for more information about the Telemetry service
-
If necessary, you can opt out of remote health reporting.
-
If you need to enable external access to node ports, configure ingress cluster traffic by using a node port.
-
If you did not configure {rh-openstack} to accept application traffic over floating IP addresses, configure {rh-openstack} access with floating IP addresses.