You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Cilium BGP loadbalancing, nodes that join the cluster following the initial call to EnsureLoadBalancer are not getting the shared IP address applied.
Have you removed all sensitive information, including but not limited to access keys and passwords?
Have you checked to ensure there aren't other open or closed Pull Requests for the same bug/feature/question?
Bug Reporting
Expected Behavior
Applicable new nodes should get the shared IP assigned when they join the cluster if a cilium BGP Load Balancer exists.
Actual Behavior
New nodes are not getting the shared IP assigned.
Steps to Reproduce the Problem
Deploy CCM with cilium BGP load balancing enabled
Deploy a sample deployment such as nginx
Create a service of type LoadBalancer to expose the sample deployment
Scale up the cluster to add a new node
Observe the new node does not get the shared IP attached to it in the Linode Cloud Manager.
General:
When using Cilium BGP loadbalancing, nodes that join the cluster following the initial call to EnsureLoadBalancer are not getting the shared IP address applied.
Bug Reporting
Expected Behavior
Applicable new nodes should get the shared IP assigned when they join the cluster if a cilium BGP Load Balancer exists.
Actual Behavior
New nodes are not getting the shared IP assigned.
Steps to Reproduce the Problem
Environment Specifications
Screenshots, Code Blocks, and Logs
Additional Notes
For general help or discussion, join the Kubernetes Slack team channel
#linode
. To sign up, use the Kubernetes Slack inviter.The Linode Community is a great place to get additional support.
The text was updated successfully, but these errors were encountered: