$ export MINISHIFT_ENABLE_EXPERIMENTAL=y
If you want to get early access to some upcoming features and experiment, you can set the environment variable
MINISHIFT_ENABLE_EXPERIMENTAL, which makes additional features flags available:
$ export MINISHIFT_ENABLE_EXPERIMENTAL=y
Experimental features are not officially supported, and might break or result in unexpected behavior. To share your feedback on these features, you are welcome to contact the Minishift community.
By default, Minishift does not expose all
oc cluster up flags in the Minishift CLI.
You can set the
MINISHIFT_ENABLE_EXPERIMENTAL environment variable to enable the following options for the
minishift start command:
Enables passing flags directly to
oc cluster up that are not directly exposed in the Minishift CLI.
For example, following command will pass the
--service-catalog flag to
oc cluster up to provision the OpenShift service catalog:
$ MINISHIFT_ENABLE_EXPERIMENTAL=y minishift start --extra-clusterup-flags "--service-catalog"
Since the Internal Virtual Switch for Hyper-V does not provide a DHCP offer option, an IP address needs to be provided in a different way. For Hyper-V a functionality is provided to assign an IP address on startup using the Data Exchange Service.
This only works with the CentOS or RHEL ISO in combination with Hyper-V. The B2D image experiences a problem when the values are being sent to the Minishift instance and consumed by the B2D iso. We are looking into the issue and hope to provide a solution in the future.
To make this work you need to create a Virtual Switch using NAT.
WinNAT is limited to one NAT network per host. For more details about capabilities, and limitations, please see the WinNAT capabilities and limitations blog.
The following command will attempt to assign an IP address for use on the Internal Virtual Switch 'MyInternal':
PS> $env:MINISHIFT_ENABLE_EXPERIMENTAL="y" PS> $env:HYPERV_VIRTUAL_SWITCH="MyInternal" PS> minishift.exe start ` --iso-url centos ` --network-ipaddress 192.168.1.10 ` --network-gateway 192.168.1.1 ` --network-nameserver 184.108.40.206
If you want to use the 'DockerNAT' network, the following commands are needed to setup the correct NAT networking and assign an IP in the range expected:
PS> New-NetNat -Name SharedNAT -InternalIPInterfaceAddressPrefix 10.0.75.1/24 PS> $env:MINISHIFT_ENABLE_EXPERIMENTAL="y" PS> $env:HYPERV_VIRTUAL_SWITCH="DockerNAT" PS> minishift.exe start ` --iso-url centos ` --network-ipaddress 10.0.75.128 ` --network-gateway 10.0.75.1 ` --network-nameserver 220.127.116.11
Be sure to specify a valid gateway and nameserver. Failing to do so will result in connectivity issues.
This only works with the CentOS or RHEL ISO and is currently not supported on KVM as the driver plugin relies on the DHCP offer to determine the IP address.
Most hypervisors do not support extending the lease time when the IP is assigned using DHCP. This might lead to a new IP getting assigned to the VM after a restart as it will conflict with the security certificates generated for the old IP. This will make Minishift completely unusable.
For this purpose, Minishift includes the functionality to set a static address to the VM. This will prevent it from changing between restarts. However, it will not work on all the driver plugins at the moment due to the way the IP address is resolved.
The following command will set the IP address that was assigned as fixed:
$ minishift ip --set-static
If you prefer to use dynamic assignment, you can use:
$ minishift ip --set-dhcp
Minishift provides a DNS server for offline usage or possible overriding DNS records while testing. This will allow you to access the OpenShift routes without Internet.
The DNS server is specific to a profile.
Starting the DNS server can be done as follows:
$ minishift dns start
After starting the DNS server you need to configure your device settings to use this nameserver. The start command will show you a temporary option that can be used when you entered offline usage.
In the current implementation you need to start the server and do required changes in the host settings manually. The DNS configuration is not permanent and might reset when the network state of the device changes
Stopping the DNS server can be done as follows:
$ minishift dns stop
To get the status of the DNS server:
$ minishift dns status