Explicitly set etcd authentication
Bug #1759813 reported by
Spyros Trigazis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Magnum | Status tracked in Rocky | |||||
Queens |
Fix Committed
|
Critical
|
Spyros Trigazis | |||
Rocky |
Fix Released
|
Critical
|
Spyros Trigazis |
Bug Description
Update etcd configuration:
Set authentication to true for both client and peer connections, set trusted_ca for both client and peer.
Without client and peer auth, etcd listens over ssl but it is not using the certs for authentication.
curl -k https://<IP>:2379/v2/keys/ was working and with the v3 api you can access the kubernetes objects.
Before running etcd in a container, the auth was set to true by etcd, the default change from the syscontainer:
https:/
Changed in magnum: | |
status: | New → Triaged |
importance: | Undecided → Critical |
description: | updated |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/557677
Review: https:/