-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BGPv2: Updates CiliumBGPNodeConfigOverride Type #31598
Conversation
/test |
/ci-ginkgo |
c72e9f4 added this field to CiliumNode after this PR was pushed. I'm going to rebase to see if the commit resolves this CI flake. |
Previously, the CiliumBGPNodeConfigOverrideSpec included the `nodeRef` field for referencing the name of the node for which the BGP configuration is overridden. This approach introduces the potential for conflicts by multiple CiliumBGPNodeConfigOverride resources referencing the same CiliumBGPNodeConfig. This PR removes the `nodeRef` field and updates the CiliumBGPNodeConfigOverride spec so users understand that the name of the CiliumBGPNodeConfig and CiliumBGPNodeConfigOverride must match for the configuration overrides to be applied. Signed-off-by: Daneyon Hansen <daneyon.hansen@solo.io>
a7f4feb
to
364fb04
Compare
/test |
1 similar comment
/test |
/ci-clustermesh |
@YutaroHayakawa since #31684 requires this PR, it would be great to get this merged. cc: @joestringer |
It still needs the review from sig-k8s. Let me ping @tommyp1ckles. |
@YutaroHayakawa do you have any suggestions for someone else to review this PR? |
Ok, Tom is not available now. Let me randomly select a person from sig-k8s and request a review from @squeed 🙏 |
This needs a proper release note, unless we are removing a field that was never released, as well as an entry in the UPGRADING notes. Usually we first mark a field as deprecated for one release, then remove the field. As this is v2alpha1 that may be loosened, but only for good reason. |
@squeed yes, this is a change to an unreleased API type. |
Easy. Approved, thanks. |
Previously, CiliumBGPNodeConfigOverrideSpec included the
nodeRef
field for referencing the name of a CiliumBGPNodeConfig to override. This approach introduces the potential for conflicts by multiple CiliumBGPNodeConfigOverride resources referencing the same CiliumBGPNodeConfig.This PR removes the
nodeRef
field and updates the CiliumBGPNodeConfigOverride spec so users understand that the name of the CiliumBGPNodeConfig and CiliumBGPNodeConfigOverride must match for the configuration overrides to be applied.