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

Automated cherry pick of #3700: Determine conformance container image version at runtime #3701: Use default dnsPolicy for AKS #3718

Merged
merged 2 commits into from
Apr 29, 2022
Merged

Automated cherry pick of #3700: Determine conformance container image version at runtime #3701: Use default dnsPolicy for AKS #3718

merged 2 commits into from
Apr 29, 2022

Commits on Apr 29, 2022

  1. Determine conformance container image version at runtime 

    Since Sonobuoy 0.20, Sonobuoy releases are no longer attached to
Kubernetes releases and can determine the images at runtime according to
the Kubernetes server's version. This patch removes pinned K8s test
image versions to fix compatability issues caused by version skew.

Signed-off-by: Quan Tian <qtian@vmware.com>
    @tnqn
    tnqn committed Apr 29, 2022
    Configuration menu
    Copy the full SHA
    888fe53 View commit details
    Browse the repository at this point in the history

  2. Use default dnsPolicy for AKS 

    AKS overrides KUBERNETES_SERVICE_HOST with a FQDN value. Using
ClusterFirstWithHostNet would lead to antrea-agent start failure.

Signed-off-by: Quan Tian <qtian@vmware.com>
    @tnqn
    tnqn committed Apr 29, 2022
    Configuration menu
    Copy the full SHA
    7fd921f View commit details
    Browse the repository at this point in the history