to create MOST of the config, but what i can't specify is the ca_file
I am proposing a new config option like this
juju config containerd \
custom_registries='[{"url": "my.custom.registry", "username": "*****", "password": "********"
"ca_file": "'$(base64 < my.custom.registry.pem)'"}]'
so that the charm does this:
[plugins.cri.registry.configs] [plugins.cri.registry.configs."my.custom.registry".tls]
ca_file = "/etc/containerd/my.custom.registry.pem"
creates a file on the filesystem /etc/containerd/my.custom.registry.pem
with the value of the base64.b64_decode( ca_file_config )
working with @kwmonroe yesterday
we downloaded crictl to tmp and were able to use it to pull images once we got the config correct:
# list images /run/containerd /containerd. sock images
/tmp/crictl -r -r unix://
# delete images /run/containerd /containerd. sock delete my.custom. registry/ busybox: latest
/tmp/crictl -r -r unix://
# pull images /run/containerd /containerd. sock pull my.custom. registry/ busybox: latest
/tmp/crictl -r -r unix://
With these tools we were able to determine the appropriate config necessary for a custom_registry that was using a self-signed cert
I can use the charm's current config
juju config containerd \ registries= '[{"url" : "my.custom. registry" , "username": "*****", "password": "********"}]'
custom_
to create MOST of the config, but what i can't specify is the ca_file
I am proposing a new config option like this registries= '[{"url" : "my.custom. registry" , "username": "*****", "password": "********" registry. pem)'"} ]'
juju config containerd \
custom_
"ca_file": "'$(base64 < my.custom.
so that the charm does this: plugins. cri.registry. configs]
[plugins. cri.registry. configs. "my.custom. registry" .tls] d/my.custom. registry. pem"
[
ca_file = "/etc/container
creates a file on the filesystem /etc/containerd /my.custom. registry. pem
with the value of the base64.b64_decode( ca_file_config )