Question
DO k8s pull from private registry
Hi, has anyone come across this type of issue:
I am trying to setup k8s cluster and I also have a private registry running on a droplet, when I try to deploy an image from my private registry I get this error
Error response from daemon: Get https://artifacotry_ip: http: server gave HTTP response to HTTPS client
ok so I thought I am gonna setup a reverse proxy and add a self-signed certificate to it, you will think yeah this should solve the issue above, which it did, BUT it brings a new issues instead when I deploy again
Error response from daemon: Get https://artifactory_ip: x509: certificate signed by unknown authority
so because k8s is a managed service of digitalocean, I don’t have access to master node to push my certificates there and as you know I cannot ssh to k8s droplets either.
Anyone has any idea how to solve this issue?
Thank you.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×
@jkwiatkoski
is it not possible for the K8s cluster to pull images from a private container registry running in a droplet in the same VPC ?
Assuming we have setup TLS on the Private Container Registry using a self-signed cert?
So we would have to tell the K8s cluster to use that self-signed cert to do the image pull…
Thanks in advance