mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
25 lines
1.4 KiB
Plaintext
25 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_ibm_cloud/installing-ibm-cloud-private.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="private-clusters-about-ibm-power-virtual-server_{context}"]
|
|
= Private clusters in {ibm-power-server-title}
|
|
|
|
To create a private cluster on {ibm-power-server-name}, you must provide an existing private Virtual Private Cloud (VPC) and subnets to host the cluster. The installation program must also be able to resolve the DNS records that the cluster requires. The installation program configures the Ingress Operator and API server for only internal traffic.
|
|
|
|
The cluster still requires access to internet to access the {ibm-cloud-name} APIs.
|
|
|
|
The following items are not required or created when you install a private cluster:
|
|
|
|
* Public subnets
|
|
* Public network load balancers, which support public Ingress
|
|
* A public DNS zone that matches the `baseDomain` for the cluster
|
|
|
|
You will also need to create an {ibm-name} DNS service containing a DNS zone that matches your `baseDomain`. Unlike standard deployments on Power VS which use {ibm-name} CIS for DNS, you must use {ibm-name} DNS for your DNS service.
|
|
|
|
[id="private-clusters-limitations-ibm-power-virtual-server_{context}"]
|
|
== Limitations
|
|
|
|
Private clusters on {ibm-power-server-name} are subject only to the limitations associated with the existing VPC that was used for cluster deployment.
|