Helm upgrade fails when Boots is in hostNetwork mode

[jacobweinstock]

The deployment strategy of Boots, when run in hostNetwork mode and if the new pod gets scheduled on the same node as the old pod, doesn't allow for upgrading. The new pod will always fail as the required ports are already in use by the existing Boots pod. In hostNetwork mode we will probably need to use the recreate strategy. I dont believe we specify a strategy soRollingUpdate is the default. RollingUpdate for Boots when it is not using hostNetwork mode, should be just fine.

Expected Behaviour

Current Behaviour

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

• Operating System and version (e.g. Linux, Windows, MacOS):

• How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:

• Link to your project or a code example to reproduce issue: