https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
t
(yeah, I run it with 
k3d
)
a
stock k3s is containerd, wich can be configured for private ca https://docs.k3s.io/installation/private-registry?_highlight=containerd
Maybe ask in #k3d ? (k3d uses docker, i guess config is different)
t
Yeah, I asked already but did not have any answer yet, and was not completely sure if this is k3d or k3s question. Thanks for the link, I'll see if it is related.
c
Yes, you would need to inject the CA files (and registries.yaml configuration if necessary) into all of the k3s pods running in k3d.
a
t
Thank you, gonna try with registries k3d link. So if CA is added to registry configuration, it is automatically propagated to helm job pod and pods it creates?
c
no. the registry configuration is for containerd, which is what does the actual pulling of images used by pods.
👍 1
t
OK, I will give it a try at Monday and update the thread. Long weekend this time ¯\_(ツ)_/¯
Thank you, it works well.
5 Views
Open in Slack
PreviousNext
Powered by