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

Bug 1868158: gcp, azure: Handle azure vips similar to GCP #2011

Merged
merged 1 commit into from
Sep 10, 2020
Merged

Bug 1868158: gcp, azure: Handle azure vips similar to GCP #2011

merged 1 commit into from
Sep 10, 2020

Commits on Sep 10, 2020

  1. gcp, azure: Handle azure vips similar to GCP

    This PR does the following things:
    
    - Rename gcp-routes-controller to apiserver-watcher, since it is generic
    - Remove obsolete service-management mode from gcp-routes-controller
    - Change downfile directory to /run/cloud-routes from /run/gcp-routes
    - Write $VIP.up as well as $VIP.down
    - Add an azure routes script that fixes hairpin.
    
    Background: Azure hosts cannot hairpin back to themselves over a load
    balancer. Thus, we need to redirect traffic to the apiserver vip to
    ourselves via iptables. However, we should only do this when our local
    apiserver is running.
    
    The apiserver-watcher drops a $VIP.up and $VIP.down file, accordingly,
    depending on the state of the apiserver. Then, we add or remove iptables
    rules that short-circuit the load balancer.
    
    Unlike GCP, we don't need to do this for external traffic, only local
    clients.
    squeed authored and cgwalters committed Sep 10, 2020
    Configuration menu
    Copy the full SHA
    be57854 View commit details
    Browse the repository at this point in the history