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

[release-4.7] Bug 1932649: Canary: Add edge termination to canary route #558

Merged

Commits on Feb 24, 2021

  1. Add edge termination to canary route

    This commit adds edge termination to the canary route. If you use an external loadbalancer that redirects all http traffic to https (us in our case) this route will not serve its purpose and the openshift-ingress-operator will be degraded during an upgrade.
    Setting it to 'edge' termination should always work.
    jomeier authored and sgreene570 committed Feb 24, 2021
    Configuration menu
    Copy the full SHA
    f8d887b View commit details
    Browse the repository at this point in the history
  2. Call: 'make generate'.

    jomeier authored and sgreene570 committed Feb 24, 2021
    Configuration menu
    Copy the full SHA
    4fc6277 View commit details
    Browse the repository at this point in the history
  3. canary: Skip TLS verification in canary HTTP client

    Commit c98416 switched the canary route from a cleartext route
    to an edge terminated route. In order for canary probes to succeed, the
    canary client needs to skip TLS verification, since the router's default
    certificate may be a self-signed certificate. This change is temporary, since
    ideally the router's default certificate (or a new certificate for the canary
    route) would be added to the canary client's trust bundle.
    sgreene570 committed Feb 24, 2021
    Configuration menu
    Copy the full SHA
    8a2f2f7 View commit details
    Browse the repository at this point in the history