Description of problem:

The BGP reconnect timer has been added to Metallb in the OCP version 4.17. The timer can be set CRD metallb bgppeer or in the FRR frrcongifuration. The metallb bgppeer is not adding the connect time command.

Version-Release number of selected component (if applicable): 4.17

How reproducible: 

Easily with the metallb operator version 4.17

Steps to Reproduce:
1. Deploy metallb-operator
2. Deploy metallb with frr
3. Apply a bgppeer with the connectTimer set to less then the default 120s
Actual results:

BGP peer comes up with all values set in the bgppeer except for the connect time timer.

Expected results:

Metallb should configure BGP retry connection timer.

Expect the meta

Additional info:

When apply the frrconfiguration after the metallb bgppeer you receieve the following error message. 

$ oc apply -f frrconfig-allow-all.yaml 
Error from server (Forbidden): error when creating "frrconfig-allow-all.yaml": admission webhook "frrconfigurationsvalidationwebhook.metallb.io" denied the request: multiple connect times specified for neighbor 10.46.81.131 at vrf 
resource is invalid for node worker-0

When applying only the frrconfiguration the connect timer is configured correctly on the bgp peer in the frr configuration.

carlosgoncalves was able to successfully add the connect timer with the metallb bgppeer using a 4.16 version.