fix: correct CiliumBGPNodeConfigOverride CRD wait condition and deprecate legacy BGP Peering Policy (#13366)

* fix: correct CiliumBGPNodeConfigOverride CRD wait condition and deprecate legacy BGP Peering Policy

- Fix copy-paste bug where cilium_bgp_advertisements was used instead of
  cilium_bgp_node_config_overrides when waiting for the
  CiliumBGPNodeConfigOverride CRD. This caused the CRD readiness check
  to be skipped when only node config overrides were configured.
- Add deprecation notices across docs, sample inventory, and defaults
  to guide users away from the legacy v2alpha1 CiliumBGPPeeringPolicy
  toward the supported BGP v2 API variables.

* fix(cilium): simplify BGP node override condition
This commit is contained in:
Dasmat Hansda
2026-09-26 10:00:27 +00:00
committed by GitHub
parent d75f23cba3
commit e62c778293
4 changed files with 10 additions and 2 deletions
+4
View File
@@ -172,6 +172,10 @@ For further information, check [BGP Control Plane Resources documentation](https
### BGP Peering Policies (Legacy < v1.16)
> **Warning:** The `cilium_bgp_peering_policies` variable uses the deprecated `CiliumBGPPeeringPolicy` (`cilium.io/v2alpha1`) CRD.
> Starting with Cilium v1.16, this CRD is deprecated and generates warnings in Cilium logs.
> Migrate to the new BGP v2 API using `cilium_bgp_cluster_configs`, `cilium_bgp_peer_configs`, `cilium_bgp_advertisements`, and `cilium_bgp_node_config_overrides`.
Cilium's BGP Peering Policies can be configured with the `cilium_bgp_peering_policies` variable:
```yml