Common name in kubernetes certificates is invalid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
In Progress
|
Undecided
|
Spyros Trigazis |
Bug Description
In kubernetes with atomic we have a set of certificates that we use in three places:
1. etcd
2. kubernetes apiserver
3. kubernetes service accounts
In order to make service accounts work we need to set the common name properly in the certificates.
example failure for a service running in a cluster which failed:
Caused by: javax.net.
certificate: sha1/IP/
DN: CN=kubernetes.
Reference cert configuration in CoreOS docs:
https:/
We need similar changes in CoreOS drivers and openSUSE.
http://
http://
Changed in magnum: | |
assignee: | nobody → Mathieu Velten (matmaul) |
status: | New → In Progress |
Changed in magnum: | |
assignee: | Mathieu Velten (matmaul) → Spyros Trigazis (strigazi) |
Reviewed: https:/ /review. openstack. org/484307 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=a7ab475cd09 17ffdeb1dd5ffa5 a8a9a38f907b78
Committed: https:/
Submitter: Jenkins
Branch: master
commit a7ab475cd0917ff deb1dd5ffa5a8a9 a38f907b78
Author: Mathieu Velten <email address hidden>
Date: Mon Jul 17 10:53:21 2017 +0200
Use kubernetes service name in cert request
In kubernetes with atomic we have a set of certificates that we use in
three places:
1. etcd
2. kubernetes apiserver
3. kubernetes service accounts
In order to make service accounts work we need to set the common name
properly in the certificates.
Partial-Bug: #1705694
Change-Id: I04ed3bba938f0d 5f340e2141be940 58c38c2ed2b