Private registry configuration

[stefanvangastel]

Hi, first: love this helpful yet easy to use solution.

But.. I don't seem to be able to get this to run with a private registry.

Current setup:

• We run offline, on-prem
• Deploying in a Rancher custom Kubernetes cluster (RKE)
• Created a ConfigMap to get the config.yml in my container
• Deployment mounting the configmap to /config exposing /config/config.yml
• Added ServiceAccount and RBAC config to provide permissions to read namespaces etc

We use Gitlab as our private registry, exposed under registry.company.nl, so images look like this: registry.company.nl/ubuntu:18.04.

What would my config.yml look like? Since your application is running and it can find the images but wants to lookup newer version on https://registry.hub.docker.com/v2/ubuntu:18.04

PS: Do you have a Helm chart for this? Or need help building one?

[arminc]

Hi @stefanvangastel You can choose to look for new versions online or you can decide to only look in your own private registry. The reason it defaults online is because that is probably the upstream source, which gets updated first. If you don't want that then make sure you are proxying the upstream registries so you can get the info trough your own private registry or regularly pull/push from them into your private registry.

As for the config, if you only want to use your own private registry you can do something like this:

imageRegistries:
  dockerHub: 
    default: false
  override: 
    - registry:
        name: PrivateRegistryName
        url: registry.company.nl
      images:
        - .*

With this config all the image names will match to 'PrivateRegistryName' and will do a search on 'registry.company.nl'

P.S. I still want to refactor some code to make the finding versions more logical, the flow logical and expandable, printing to be clean, and then start on the Helm chart. But if you have time a Helm chart would be much appreciated as it is one of the early stories :) #12

[stefanvangastel]

Ok, that works! Thanks. Now I'n running into TLS issues due to internal CA signed certs. I'll have a look into loading our CA into the container