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

Restore compatibility in specifying custom CAs by using Go client #1735

Merged
merged 3 commits into from
May 12, 2021
Merged

Restore compatibility in specifying custom CAs by using Go client #1735

merged 3 commits into from
May 12, 2021

Commits on Apr 25, 2021

  1. Go back to using scratch space and Go client for custom CAs 

    This restores support for the following scenarios:
- Now the system certs are considered as valid when a custom
CA is used.
- The custom CA will be accepted regardless of the key value
used in the configmap.

Add a test for the second scenario.

Signed-off-by: Maya Rashish <mrashish@redhat.com>
    @maya-r
    maya-r committed Apr 25, 2021
    Configuration menu
    Copy the full SHA
    416945a View commit details
    Browse the repository at this point in the history

  2. Try to make it clearer that we only want one value 

    Signed-off-by: Maya Rashish <mrashish@redhat.com>
    @maya-r
    maya-r committed Apr 25, 2021
    Configuration menu
    Copy the full SHA
    cc2917b View commit details
    Browse the repository at this point in the history

Commits on May 9, 2021

  1. Update docs, pointed out by Alex Kalenyuk. 

    Signed-off-by: Maya Rashish <mrashish@redhat.com>
    @maya-r
    maya-r committed May 9, 2021
    Configuration menu
    Copy the full SHA
    9c75193 View commit details
    Browse the repository at this point in the history