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

Bug 1797801: Update the Hive and reporting-operator charts to work with single-stack ipv4 and ipv6. #1092

Merged
merged 1 commit into from Feb 17, 2020
Merged

Bug 1797801: Update the Hive and reporting-operator charts to work with single-stack ipv4 and ipv6. #1092

merged 1 commit into from Feb 17, 2020

Commits on Feb 16, 2020

  1. charts: Update the Hive and reporting-operator helm charts to work wi… 

    …th single-stack ipv4 and ipv6.

This is a follow-up to PR kube-reporting#1077 which introduced support for using S3 as the storage backend in a IPV6 cluster. The changes in this PR update the Hive ghostunnel configuration needed to support both a single-stack configuration, dependent on the value of the top-level .useIPV6Networking.

In the case of the pkg/reporting-operator/cmd.go flags, we typically override the default values through the corresponding environment variable, which is reflected in the reporting-operator deployment changes. It's important to note that this means we need to be more careful when interacting with the CLI explicitly (i.e. in the case of running the reporting-operator locally, or in the e2e suite.)
    @timflannagan
    timflannagan committed Feb 16, 2020
    Copy the full SHA
    8cb021c View commit details
    Browse the repository at this point in the history