[fabio ziviello] Deploy a local registry #155

Activity

1. sciabarracom

   assigned

   d4rkstar

   on Jul 19, 2025
2. fziviello commented on Jul 19, 2025

   

   fziviello

   on Jul 19, 2025

   More actions

   working on it
3. sciabarracom

   changed the title [-]Deploy a local registry[/-] [+][fabio ziviello] Deploy a local registry[/+] on Jul 19, 2025
4. sciabarracom commented on Jul 22, 2025

   

   sciabarracom

   on Jul 22, 2025

   ContributorAuthor

   More actions

   To access a registry we will have to make it public, so please use an ingress named img.<apiphost> (a 3 letter because are reserved for internal services) and protect the registry with a randomly generated secret. Then create a service account for the invoker and assign the secret to access the registry
5. sciabarracom commented on Jul 22, 2025

   

   sciabarracom

   on Jul 22, 2025

   ContributorAuthor

   More actions

   We always use ssl, except in miniops. SInce it is local, we have to use http so the docker registry will aways be insecure and cannt be used unless we explicitly instruct the containerd in kind to use an insecure registry.
   So we have to change the kind setup to add those configurations:

   containerdConfigPatches:
   - |-
     [plugins."io.containerd.grpc.v1.cri".registry.mirrors."10.52.212.167:9000"]
       endpoint = ["http://10.52.212.167:9000"]
     [plugins."io.containerd.grpc.v1.cri".registry.configs."10.52.212.167:9000".tls]
       insecure_skip_verify = true 
   

   https://medium.com/@nash.checkin/kind-kubernetes-in-docker-pulling-image-from-private-insecure-registry-2711706629cb
6. sciabarracom

   closed this as completedon Jul 22, 2025