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

data/bootstrap: update etcd-signer-server to use certs for api and api-int #1670

Merged

Commits on Apr 24, 2019

  1. data/bootstrap: update etcd-signer-server to use certs for api and ap…

    …i-int
    
    Requires etcd-signer-server to support multiple certs for serving [1]
    
    Currently the etcd-signer-server only serves request using `api-int` serving certificate which causes errors like,
    
    ```console
    time="2019-04-24T13:25:11-07:00" level=debug msg="Still waiting for the Kubernetes API: Get https://api.adahiya-0.tt.testing:6443/version?timeout=32s: x509: certificate is valid for api-int.adahiya-0.tt.testing, not api.adahiya-0.tt.testing"
    ```
    
    as the installer is hitting the etcd-signer-server on api.$cluster_domain.
    
    Setting up etcd-signer-server to use multiple certs ie one for api and another for api-int allows both internal and external client to hot etcd-signer-server and not get x509 errors.
    
    [1]: coreos/kubecsr#28
    abhinavdahiya committed Apr 24, 2019
    Configuration menu
    Copy the full SHA
    5ff1ae2 View commit details
    Browse the repository at this point in the history