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.

Sign up for GitHub

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

Jump to bottom

[release-2.6] 🐛: elbv2: wait for LB active state instead of resolving DNS name #5226

Open
wants to merge 1 commit into
base: release-2.6
Choose a base branch
from
Open

[release-2.6] 🐛: elbv2: wait for LB active state instead of resolving DNS name #5226

wants to merge 1 commit into from

Commits on Nov 22, 2024

  1. 🐛elbv2: wait for LB active state instead of resolving DNS name 

    Using DNS name resolution as a way to check the load balancer is working
can cause problems that are dependent on the host running CAPA. In some
systems, the DNS resolution can fail with very large TTLs cached DNS
responses, causing very long provisioning times.

Instead of DNS resolution, let's use the AWS API to check for the load
balancer "active" state. Waiting for resolvable DNS names should be left
for the clients to do.
    @r4f4
    r4f4 authored and k8s-infra-cherrypick-robot committed Nov 22, 2024
    Configuration menu
    Copy the full SHA
    a38f759 View commit details
    Browse the repository at this point in the history