Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-4399

Investigate local registry support in peer-pods/CoCo

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • guest-components
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Operators like Openshift AI deploy/enable local openshift registy, which caches the container images in a local cluster-accessible server for faster deployment. Usually the server is accessed via image-registry.openshift-image-registry.svc:5000

      There are a lot of problems when this is used:

      • A lot of applications (like in OAI but not only) default on using local registry
      • Such server is not available to peer pods CVMs
      • Even if it was, breaks Trustee image signature policy
      • In any case even if this works, image pulling is not faster because the podvm still needs to pull from the worker node.

      The main issue is that it looks like this local registry overrides all the default images, for example in the web UI if you create a new pod, the default example that pops up has the local server.

              Unassigned Unassigned
              eesposit@redhat.com Emanuele Giuseppe Esposito
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: