Open jeffcpullen opened 4 years ago
I resolved this temporarily by removing the volume mount at /etc/ssl
in deployment. This will result in a new cert being created each restart which takes time.
I don't think we want it generating certs anyways. What do you think of using the service secret annotation and just having all the pods leverage that? That is what I pushed in commit 20c627db8ac199c198d6e8d3e56f3865333578c4
Agreed! The container image has been adjusted accordingly to accept a mount at /etc/ssl/certs
by default.
Rather than having certificates generated by the image or letsencrypt it seems like it would make more sense to have OCP generate them and mount them in /etc/ssl/certs and /etc/ssl/private.
Pod fails to start without those certificates.