You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 23, 2024. It is now read-only.
If you open the browser and go to https://: it will display the certificate details of the other service that it internally contacted inside the Kubernetes cluster.
I found that the server wasn't responding.
Nor when I try and curl the service from the Ubuntu virtual machine.
It looks like the certificate rotation mechanism might not be working properly:
sysadmin@ubuntu-1804-srv:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-workload-deployment-6d6794b959-qjt84 1/1 Running 0 63m
ping-deployment-dfb6c6457-tnlzn 1/1 Running 0 13m
pong-deployment-659c57bc67-9n7pk 1/1 Running 0 13m
sysadmin@ubuntu-1804-srv:~$ kubectl logs ping-deployment-dfb6c6457-tnlzn
2020/03/31 17:36:03 tls: failed to find any PEM data in certificate input
2020/03/31 17:36:03 tls: failed to find any PEM data in certificate input
2020/03/31 17:37:27 Certificate renewed
2020/03/31 17:37:27 http: Server closed
2020/03/31 17:37:27 http: Server closed
sysadmin@ubuntu-1804-srv:~$ kubectl logs pong-deployment-659c57bc67-9n7pk
2020/03/31 17:36:03 tls: failed to find any PEM data in certificate input
2020/03/31 17:36:03 tls: failed to find any PEM data in certificate input
2020/03/31 17:37:34 Certificate renewed
2020/03/31 17:37:34 http: Server closed
2020/03/31 17:37:34 http: Server closed
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In https://github.com/jetstack/cert-manager-nginx-plus-lab#testing-the-deployment-1
I found that the server wasn't responding.
Nor when I try and curl the service from the Ubuntu virtual machine.
It looks like the certificate rotation mechanism might not be working properly:
The text was updated successfully, but these errors were encountered: