Bug 1707573: *: remove deprecated EtcdCA and promote EtcdSigner#1720
Bug 1707573: *: remove deprecated EtcdCA and promote EtcdSigner#1720openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
ee10d76 to
300857d
Compare
|
buildcop here - looks like the https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_installer/1720/pull-ci-openshift-installer-master-e2e-aws/5697 test failed due to a crash in the installer: |
|
From the bootstrap gather: $ wget https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_installer/1720/pull-ci-openshift-installer-master-e2e-aws/5706/artifacts/e2e-aws/installer/bootstrap-logs.tar
$ tar xf bootstrap-logs.tar
$ tail -n3 control-plane/ip-10-0-137-34.ec2.internal/containers/etcd-member.log
2019-05-07 20:05:04.609226 I | embed: rejected connection from "10.0.137.34:53114" (error "remote error: tls: bad certificate", ServerName "etcd-0.ci-op-l9xy353n-1d3f3.origin-ci-int-aws.dev.rhcloud.com")
2019-05-07 20:07:11.852718 I | mvcc: store.index: compact 10800
2019-05-07 20:07:11.858636 I | mvcc: finished scheduled compaction at 10800 (took 4.682041ms)So something seems broken here. |
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
@abhinavdahiya found we were base64 encoding configmap |
|
/lgtm This should be okay to merge if it goes green. :) |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, hexfusion The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test e2e-openstack |
|
e2e-aws: known flake :( /retest |
|
e2e-aws-upgrade failing due to load balancer not getting setup: /retest |
Currently, etcd has 2 CAs
EtcdCAand EtcdSigner . This PR removed the deprecatedEtcdCAand promotesEtcdSigneras the one signer for etcd server TLS assets. To maintain backward compatibility we will honor the oldetcd-clientSecret naming for ApiServer to consume.This is important because currently, we do not store the etcd CA key on the cluster making disaster recovery very complicated. By having the key on cluster etcd server certs can be regenerated.
/cc @deads2k @wking @abhinavdahiya