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

support TLS for components and downstream db #931

Merged
merged 4 commits into from
Mar 17, 2020
Merged

Commits on Mar 15, 2020

  1. support TLS for components (#904)

    truely support TLS for components.
    before this pr if enable TLS for components
    
    - `tidb` will fail to connect to `pump`
    - no TLS between drainer and pump
    - no enable TLS for tikv client in `drainer`
    - `binlogctl` can't work actually
    ...
    
    [relate docs](https://pingcap.com/docs/stable/how-to/secure/enable-tls-between-components/) ([Chinese version](https://pingcap.com/docs-cn/stable/how-to/secure/enable-tls-between-components/))
    This Commit:
    - properly handle things about TLS when enabling TLS
    - enable TLS in the integration tests
    - log pump config at startup time
    july2993 committed Mar 15, 2020
    Configuration menu
    Copy the full SHA
    738f0ca View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    7e30098 View commit details
    Browse the repository at this point in the history
  3. Reload cert/key for every new conn (#927)

    * Reload cert/key for every new conn
    
    support reload cluster/downstream  TLS cert/key.
    CA still can not be hot-reload now
    
    * expand the loop
    july2993 committed Mar 15, 2020
    Configuration menu
    Copy the full SHA
    b3654f4 View commit details
    Browse the repository at this point in the history

Commits on Mar 16, 2020

  1. Configuration menu
    Copy the full SHA
    e6a357c View commit details
    Browse the repository at this point in the history