As seen previosuly in this document, there are a number of components which require an IP address which are automatically deployed on an Edge Compute Stack Host in order to provide the services at an edge location. This option requires you to edit the boot media being used to deploy the Edge Compute Stack host to provide IP addresses from the initial bring up of the Edge Compute Stack Host.
Prerequisites
Downloaded and created boot media for deploying the Edge Compute Stack host
3 IP addresses for Infrastructure Components
1 IP address for worker node configuration
Subnet Mask Information
Default Gateway Information
DNS Server(s) Information
If using the ISO deployment method you will need to extract the ISO contents, edit the KS.cfg file as outlined below and re-write the ISO file ready to be used, the instructions for this vary depending on your client computer operating system and is not currently part of this document.
Procedure
Results
Your infrastructure will be deployed using the static IP address information provided.
Example: Completed Example
A completed example of this configuration is provided below:
EC_INFRAVISOR_STATIC_IPAM_FILE="$ECS_WORK_DIR/static_ipam.json" cat <<EOT > $EC_INFRAVISOR_STATIC_IPAM_FILE { "range": ["10.211.35.74", "10.211.35.75", "10.211.35.76"], "netmask": "255.255.252.0", "gateway": "10.211.32.1", "dns": ["10.211.56.141", "10.211.81.141"] } EOT
What to do next
As part of the Edge Compute Stack deployment a kubernetes worker node is provisioned, this by default uses a DHCP address but can be changed to provide a static IP address as found in Enabling a static IP address for the default worker node.