...
User will find the network configuration file named as "user_config.sh" in the icn parent folder
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
#!/bin/bash
#Local controller - Bootstrap cluster DHCP connection
#BS_DHCP_INTERFACE defines the interfaces, to which ICN DHCP deployment will bind
#e.g. BS_DHCP_INTERFACE=${BS_DHCP_INTERFACE:-"ens513f0"}
BS_DHCP_INTERFACE=${BS_DHCP_INTERFACE:-}
#BS_DHCP_INTERFACE_IP defines the IPAM for the ICN DHCP to be managed.
#e.g. BS_DHCP_INTERFACE_IP=${BS_DHCP_INTERFACE_IP:-"172.31.1.1/24"}
BS_DHCP_INTERFACE_IP=${BS_DHCP_INTERFACE_IP:-}
#Ironic Metal3 settings for provisioning network
#Interface to which Ironic provision network to be connected
#e.g. IRONIC_INTERFACE=${IRONIC_INTERFACE:-"enp4s0f1"}
IRONIC_INTERFACE=${IRONIC_INTERFACE:-}
#Ironic Metal3 setting for IPMI LAN Network
#Interface to which Ironic IPMI LAN should bind
#e.g. IRONIC_IPMI_INTERFACE=${IRONIC_IPMI_INTERFACE:-"enp4s0f0"}
IRONIC_IPMI_INTERFACE=${IRONIC_IPMI_INTERFACE:-}
#Interface IP for the IPMI LAN, ICN verfiy the LAN Connection
#e.g. IRONIC_IPMI_INTERFACE_IP=${IRONIC_IPMI_INTERFACE_IP:-"10.10.110.20"}
IRONIC_IPMI_INTERFACE_IP=${IRONIC_IPMI_INTERFACE_IP:-} |
Kubernetes Dashboard
Kubernetes Dashboard runs on the Local Controller. It is accessed via a web browser. kubectl proxy should be running. The Dashboard is brought up by with the dashboard-deployment yaml file. This file must refer to the images in the local Docker repository (see "spec: container: image:"). There should also be a K8S service account created for an admin-user. The token for Dashboard login is created from the admin-user secrets.
...