Etcd Charm

stop listening on legacy port 4001

Bug #2008652 reported by Kevin W Monroe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Etcd Charm
In Progress
Medium
Adam Dyess
Etcd Charm 1.29

Bug Description

Etcd in ck-1.26 is listening on localhost:4001:

-----
$ sudo ss -ntlp | grep etcd
LISTEN 0 4096 127.0.0.1:4001 0.0.0.0:* users:(("etcd",pid=30531,fd=8))
LISTEN 0 4096 *:2379 *:* users:(("etcd",pid=30531,fd=9))
LISTEN 0 4096 *:2380 *:* users:(("etcd",pid=30531,fd=7))
-----

I suspect this was done for ease of debugging so you could use the localhost endpoint without needing TLS in the env. We should only listen on the current standard ports and enforce TLS while we're at it.

Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

PR to help with tls-from-localhost (thanks swalladge!):

https://github.com/charmed-kubernetes/layer-etcd/pull/204

Kevin W Monroe (kwmonroe)
no longer affects: etcd-snaps
Changed in charm-etcd:
milestone: none → 1.27
Kevin W Monroe (kwmonroe)
Changed in charm-etcd:
milestone: 1.27 → 1.27+ck1
Kevin W Monroe (kwmonroe)
Changed in charm-etcd:
milestone: 1.27+ck1 → 1.28
Adam Dyess (addyess)
Changed in charm-etcd:
milestone: 1.28 → 1.28+ck1
Revision history for this message
Adam Dyess (addyess) wrote :

Addressing with:

https://github.com/charmed-kubernetes/layer-etcd/pull/212

Adam Dyess (addyess)
Changed in charm-etcd:
status: New → In Progress
assignee: nobody → Adam Dyess (addyess)
importance: Undecided → Medium
Revision history for this message
Kevin W Monroe (kwmonroe) wrote :

PR introduces a new config option for anyone that needs to recreate the insecure 4001 endpoint. We try not to introduce new config in maint releases, so let's send this with 1.29.

Changed in charm-etcd:
milestone: 1.28+ck1 → 1.29
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.