Skip to content

fix: correct vIP filtering logic from 0.1.4#13

Merged
Handfish merged 1 commit intomainfrom
v0.1.5
Jan 17, 2026
Merged

fix: correct vIP filtering logic from 0.1.4#13
Handfish merged 1 commit intomainfrom
v0.1.5

Conversation

@Handfish
Copy link
Copy Markdown
Owner

@Handfish Handfish commented Jan 17, 2026

The 0.1.4 fix incorrectly filtered ALL endpoints from the nodes list, which removed control plane nodes that legitimately appear in both. This broke configs like:

  • endpoints: [vip, cp1, cp2, cp3]
  • nodes: [cp1, cp2, cp3, w1, w2]

The corrected logic now only filters endpoints that are NOT also in the nodes list (true vIPs/load balancers). Control plane nodes appearing in both lists are preserved.

Also fixed kubeconfig and etcd APIs to not use node targeting - these only run on control plane nodes, so targeting workers returned empty results. Added log noise filtering for HTTP/gRPC libraries.

The 0.1.4 fix incorrectly filtered ALL endpoints from the nodes list,
which removed control plane nodes that legitimately appear in both. This
broke configs like:
  - endpoints: [vip, cp1, cp2, cp3]
  - nodes: [cp1, cp2, cp3, w1, w2]

  The corrected logic now only filters endpoints that are NOT also in
the nodes list (true vIPs/load balancers). Control plane nodes appearing
in both lists are preserved.

  Also fixed kubeconfig and etcd APIs to not use node targeting - these
only run on control plane nodes, so targeting workers returned empty
results. Added log noise filtering for HTTP/gRPC libraries.
@Handfish Handfish merged commit f89b154 into main Jan 17, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant