Skip to content
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

Add HNS Load Balancer Healthchecks for ExternalTrafficPolicy: Local #99287

Merged
merged 1 commit into from Mar 17, 2022

Commits on Mar 12, 2022

  1. Fix health check from Google's Load Balancer

    This change adds 2 options for windows:
    --forward-healthcheck-vip: If true forward service VIP for health check
    port
    --root-hnsendpoint-name: The name of the hns endpoint name for root
    namespace attached to l2bridge, default is cbr0
    
    When --forward-healthcheck-vip is set as true and winkernel is used,
    kube-proxy will add an hns load balancer to forward health check request
    that was sent to lb_vip:healthcheck_port to the node_ip:healthcheck_port.
    Without this forwarding, the health check from google load balancer will
    fail, and it will stop forwarding traffic to the windows node.
    
    This change fixes the following 2 cases for service:
    - `externalTrafficPolicy: Cluster` (default option): healthcheck_port is
    10256 for all services. Without this fix, all traffic won't be directly
    forwarded to windows node. It will always go through a linux node and
    get forwarded to windows from there.
    - `externalTrafficPolicy: Local`: different healthcheck_port for each
    service that is configured as local. Without this fix, this feature
    won't work on windows node at all. This feature preserves client ip
    that tries to connect to their application running in windows pod.
    
    Change-Id: If4513e72900101ef70d86b91155e56a1f8c79719
    anfernee committed Mar 12, 2022
    1 Configuration menu
    Copy the full SHA
    78a507b View commit details
    Browse the repository at this point in the history