data/bootstrap: update etcd-signer-server to use certs for api and api-int #1670
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…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
openshift-ci-robot
added
size/XS
/hold Wait for coreos/kubecsr#28. |
openshift-ci-robot
added
the
do-not-merge/hold
|
And, once that lands and then gets percolated up into openshift/kubecsr, this: /lgtm so anyone can pull the |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
openshift/kubecsr#14 landed. /retest |
|
/test e2e-openstack |
|
/retest |
|
/hold cancel time="2019-04-26T08:00:18Z" level=info msg="Waiting up to 30m0s for the Kubernetes API at https://api.ci-op-n87yf9yy-1d3f3.origin-ci-int-aws.dev.rhcloud.com:6443..."
time="2019-04-26T08:00:48Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.ci-op-n87yf9yy-1d3f3.origin-ci-int-aws.dev.rhcloud.com:6443/version?timeout=32s: dial tcp 3.83.60.156:6443: connect: connection refused"
time="2019-04-26T08:01:28Z" level=debug msg="Still waiting for the Kubernetes API: the server could not find the requested resource"
time="2019-04-26T08:01:58Z" level=debug msg="Still waiting for the Kubernetes API: the server could ...
time="2019-04-26T08:05:30Z" level=debug msg="Still waiting for the Kubernetes API: the server could not find the requested resource"
time="2019-04-26T08:05:46Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.ci-op-n87yf9yy-1d3f3.origin-ci-int-aws.dev.rhcloud.com:6443/version?timeout=32s: dial tcp 3.210.135.62:6443: connect: connection refused"
time="2019-04-26T08:06:07Z" level=info msg="API v1.13.4+efe7dba up"without this change: time="2019-04-26T16:16:08Z" level=info msg="Waiting up to 30m0s for the Kubernetes API at https://api.ci-op-8q8923rw-1d3f3.origin-ci-int-aws.dev.rhcloud.com:6443..."
time="2019-04-26T16:16:08Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.ci-op-8q8923rw-1d3f3.origin-ci-int-aws.dev.rhcloud.com:6443/version?timeout=32s: dial tcp 3.209.122.241:6443: connect: connection refused"
time="2019-04-26T16:16:10Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.ci-op-8q8923rw-1d3f3.origin-ci-int-aws.dev.rhcloud.com:6443/version?timeout=32s: x509: certificate is valid for api-int.ci-op-8q8923rw-1d3f3.origin-ci-int-aws.dev.rhcloud.com, not api.ci-op-8q8923rw-1d3f3.origin-ci-int-aws.dev.rhcloud.com"
...
time="2019-04-26T16:19:49Z" level=debug msg="Still waiting for the Kubernetes API: Get https://api.ci-op-8q8923rw-1d3f3.origin-ci-int-aws.dev.rhcloud.com:6443/version?timeout=32s: dial tcp 3.209.122.241:6443: connect: connection refused"
time="2019-04-26T16:20:16Z" level=info msg="API v1.13.4+fcf1eaf up" |
openshift-ci-robot
removed
the
do-not-merge/hold
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/refresh |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires etcd-signer-server to support multiple certs for serving 1
Currently the etcd-signer-server only serves request using
api-intserving certificate which causes errors like,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.