-
Bug
-
Resolution: Unresolved
-
Normal
-
4.16, 4.17, 4.18
-
None
Description of problem:
The default holdtime of frr-k8s is different from the metallb one. This means that a bgppeer created without specifiying the hold time will conflict with an frrconfiguration created without specifying the hold time. This does not provide a good user experience as a user will get an error without really understanding what's wrong in his configuration.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. deploy metallb with frr-k8s as backend 2. create a bgppeer with no hold time 3. create an frr configuration with the same session details and no hold time
Actual results:
the webhook intercepts the mismatch
Expected results:
both configurations are created
Additional info:
- clones
-
OCPBUGS-38774 FRR-K8s default hold time and keepalive time different from metallb's one
- Verified
- depends on
-
OCPBUGS-38774 FRR-K8s default hold time and keepalive time different from metallb's one
- Verified
- links to