Procedure

1. To create your ovn.yaml file, run the following command:

   $ sudo cp /etc/microshift/ovn.yaml.default /etc/microshift/ovn.yaml

2. To list the contents of the configuration file you created, run the following command:

   $ cat /etc/microshift/ovn.yaml.default

   Example 'yaml' configuration file with default values

   ovsInit:
     disableOVSInit: false
     gatewayInterface: "" 1
     externalGatewayInterface: "" 2
   mtu: 1400

   1

   The default value is an empty string that means "not-specified." The CNI network plugin auto-detects to interface with the default route.

   2

   The default value is an empty string that means "disabled."

3. To customize your configuration, use the following table that lists the valid values you can use:

   Table 1.1. Supported optional OVN-Kubernetes configurations for Red Hat build of MicroShift

   Field	Type	Default	Description	Example
   ovsInit.disableOVSInit	bool	false	Skip configuring OVS bridge br-ex in microshift-ovs-init.service	true 1
   ovsInit.gatewayInterface	Alpha	eth0	Ingress that is the API gateway	eth0
   ovsInit.externalGatewayInterface	Alpha	eth1	Ingress routing external traffic to your services and pods inside the node	eth1
   mtu	uint32	1400	MTU value used for the pods	1300

   1. The OVS bridge is required. When disableOVSInit is true, OVS bridge br-ex must be configured manually.

      Important

      If you change the mtu configuration value in the ovn.yaml file, you must restart the host that Red Hat build of MicroShift is running on to apply the updated setting.

1. Access the remote cluster by running the following command:

   $ export KUBECONFIG=$PWD/kubeconfig

2. Find the name of the ovnkube-master pod that you want to restart by running the following command:

   $ pod=$(oc get pods -n openshift-ovn-kubernetes | awk -F " " '/ovnkube-master/{print $1}')

3. Delete the ovnkube-master pod by running the following command:

   $ oc -n openshift-ovn-kubernetes delete pod $pod

4. Confirm that a new ovnkube-master pod is running by using the following command:

   $ oc get pods -n openshift-ovn-kubernetes

   The listing of the running pods shows a new ovnkube-master pod name and age.

Procedure

1. Add the following settings to the /etc/systemd/system/crio.service.d/00-proxy.conf file:

   Environment=NO_PROXY="localhost,127.0.0.1"
   Environment=HTTP_PROXY="http://$PROXY_USER:$PROXY_PASSWORD@$PROXY_SERVER:$PROXY_PORT/"
   Environment=HTTPS_PROXY="http://$PROXY_USER:$PROXY_PASSWORD@$PROXY_SERVER:$PROXY_PORT/"

2. Reload the configuration settings:

   $ sudo systemctl daemon-reload

3. Restart the CRI-O service to apply the settings:

   $ sudo systemctl restart crio

Procedure

1. To install the firewalld service, run the following command:

   $ sudo dnf install -y firewalld

2. To initiate the firewall, run the following command:

   $ sudo systemctl enable firewalld --now

1. To set the IP address range:

   1. To configure the IP address range with default values, run the following command:

      $ sudo firewall-offline-cmd --permanent --zone=trusted --add-source=10.42.0.0/16

   2. Alternatively, you can configure the IP address range with custom values by running the following command:

      $ sudo firewall-offline-cmd --permanent --zone=trusted --add-source=<custom IP range>

2. To allow internal traffic from pods through the network gateway, run the following command:

   $ sudo firewall-offline-cmd --permanent --zone=trusted --add-source=169.254.169.1