The container can get stuck in a crash loop. From my dev-scripts:

    + '[' -z 172.22.0.3/24 ']'
    + '[' -z enp1s0 ']'
    + '[' -n enp1s0 ']'
    ++ ip -o addr show dev enp1s0 scope global
    + [[ -n 2: enp1s0    inet 172.22.0.153/24 brd 172.22.0.255 scope global dynamic noprefixroute enp1s0\       valid_lft 102sec preferred_lft 102sec ]]
    + ip -o addr show dev enp1s0 scope global
    + grep -q 172.22.0.3/24
    + echo 'ERROR: "enp1s0" is already set to ip address belong to different subset than "172.22.0.3/24"'
    ERROR: "enp1s0" is already set to ip address belong to different subset than "172.22.0.3/24"
    + exit 1

I'm not sure why 172.22.0.153 is already assigned. Deleting the pod does not help.

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.4
• release-4.3

Contact the Test Platform or Automated Release teams for more information.

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

• release-4.16
• release-4.17

For more information, see the branching documentation.