1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/enabling-internal-api-server-vsphere.adoc
2023-10-30 08:58:12 -04:00

23 lines
1.0 KiB
Plaintext

// Module included in the following assemblies:
//
// * windows_containers/creating_windows_machinesets/creating-windows-machineset-vsphere.adoc
:_mod-docs-content-type: PROCEDURE
[id="enabling-internal-api-server-vsphere_{context}"]
= Enabling communication with the internal API server for the WMCO on vSphere
The Windows Machine Config Operator (WMCO) downloads the Ignition config files from the internal API server endpoint. You must enable communication with the internal API server so that your Windows virtual machine (VM) can download the Ignition config files, and the kubelet on the configured VM can only communicate with the internal API server.
.Prerequisites
* You have installed a cluster on vSphere.
.Procedure
* Add a new DNS entry for `api-int.<cluster_name>.<base_domain>` that points to the external API server URL `api.<cluster_name>.<base_domain>`. This can be a CNAME or an additional A record.
[NOTE]
====
The external API endpoint was already created as part of the initial cluster installation on vSphere.
====