OPENSHIFTP-125: update docs and comments to indicate the Bastion IP i…

…s now fixed in the dhcp network Signed-off-by: Paul Bastide <[email protected]>
IBM · Jun 13, 2024 · f8d9100 · f8d9100
1 parent 3218b98
commit f8d9100
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 0 deletions.
diff --git a/README.md b/README.md
@@ -13,6 +13,8 @@ The [`ocp4-upi-compute-powervs` project](https://github.com/ibm/ocp4-upi-compute
 5. Optional: An CentOS Stream 9 Image loaded to the PowerVS Service
 6. An Existing OpenShift Container Platform Cluster installed on IBMCloud VPC with Intel architecture.
 
+The DHCP network that the automation creates is going to have the Gateway on the first IP and use the 5th IP for the bastion's Internal IP.
+
 ## Commands
 
 ### Init 

diff --git a/modules/2_pvs_prepare/network/network.tf b/modules/2_pvs_prepare/network/network.tf
@@ -26,6 +26,7 @@ resource "time_sleep" "wait_dhcp" {
   destroy_duration = "120s"
 }
 
+# The 3rd IP in this new network will be reserved for the bastion, and fixed.
 resource "ibm_pi_dhcp" "new_dhcp_service" {
   depends_on           = [time_sleep.wait_dhcp]
   pi_cloud_instance_id = var.powervs_service_instance_id