OCPBUGS-85711: Sync 2026-05-27#132
Conversation
Signed-off-by: Muhammad Adil Ghaffar <muhammad.adil.ghaffar@est.tech>
feat: Make bgp debounce configurable
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
Bump frr to 10.4.3
Add an optional LocalASN field to the Neighbor API type that instructs FRR to advertise a different ASN to a specific peer via: neighbor <peer> local-as <ASN> no-prepend replace-as Signed-off-by: Muhammad Adil Ghaffar <muhammad.adil.ghaffar@est.tech>
bgp: add localASN field to Neighbor for per-peer local-as override
Signed-off-by: PseudoResonance <75700a85-1205-4740-aebf-4413a352e81b@otake.pw>
Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
Prepare the v0.0.24 release notes
Fix CRD ASN validation for K8s v1.36.0
Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
Prepare the v0.0.25 release notes
On IPv6 single-stack clusters where nodes have no IPv4 addresses, FRR defaults the BGP router-id to 0.0.0.0. This violates RFC 6286 and RFC 4271, causing remote peers to reject the session with "Bad BGP Identifier". Derive a deterministic router-id from the node hostname using CRC32 when no explicit router-id is configured, matching the approach already used by MetalLB's native BGP implementation. Signed-off-by: Carlos Goncalves <cgoncalves@redhat.com>
Generate fallback BGP router-id on IPv6-only nodes
|
@cgoncalves: This pull request references Jira Issue OCPBUGS-85711, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgoncalves The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@cgoncalves: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
@fedepaol: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@cgoncalves: Jira Issue Verification Checks: Jira Issue OCPBUGS-85711 Jira Issue OCPBUGS-85711 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Is this a BUG FIX or a FEATURE ?:
What this PR does / why we need it:
Special notes for your reviewer:
Release note: