#Local container registry for in-dagger k3s

1 messages · Page 1 of 1 (latest)

open mauve
#

Hello everyone, I'm developing a module for an end-to-end integration test for a tool that is made by different components interacting with kubernetes. To do that I use a k3s instantiated on-demand, basically following the proposed way in the dagger related issue.

I managed to have a very nice experience, ending up to be maybe a bit more than just a utility for tests, e.g. helping develop and setting up the environments.

I'm at the point where it would be awesome if k3s could download images just built and pushed on a local registry, without relying on public ones. Is there anyone already attempting it?

I can expose the service pretty easily to the containers, but k3s looks unable to either resolve or use http insecure registries.

I'm still trying to figure out the best way, but I'd use any help I can get 🙂

edgy saddle
open mauve
#

That was my first guess, but nothing happened... Then I saw the k3s needs some additional config in /etc/rancher/k3s/registries.yaml . That allowed me to make it aware/resolve the registry name

#

Unfortunately, the insecure flag is not working apparently. This is why I was wondering if anyone tried it already... My next move will be asking k3s people otherwise

edgy saddle
edgy saddle
#

one thing that it'd be nice @open mauve is to make a k3s module in Daggerverse. Are you using modules currently?

open mauve
#

Yes I do, I think it can be generalized easily in fact

edgy saddle
open mauve
#

Cool! I'll install yours directly in my tests then 😅 after this tricky registry stuff is solved

edgy saddle
open mauve
#

@edgy saddle awesome! I'm installing the module right now, thanks!

edgy saddle
#

@open mauve some other ideas for the module: It'd be nice to have a k9s function to start k9s connected to the kube cluster 🚀