Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-8806

[KSW-Operator] Evaluate internal registry integration on OpenShift, Kubernetes and Minikube

    XMLWordPrintable

Details

    Description

      To this date, the operator in prod profile would require an external registry to build. Luckily, some cluster flavours have their own internal registry, which we should use instead of requiring one from users.

      This will improve:

      1) User experience since it's one last thing to worry about when setting up the environment
      2) Reduce network traffic, so the underlying builder won't have to connect to an external network to push GBs worth of image layers to some remote repo.
      3) Reduce build time since pushing to an external repo requires extra time

      On Minikube, if the user enabled the internal registry addon, everything works without having to provide an external registry. See KOGITO-8645 PR: https://github.com/kiegroup/kogito-serverless-operator/pull/77

      On k8s and OpenShift we should evaluate the possibilities we might have. For example, on OpenShift the default s2i builder takes care to push the built image to the internal registry. No extra configuration is needed.

      To follow up this case, we should assess the need of an old build garbage collector.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rhn-support-zanini Ricardo Zanini Fernandes
              Tristan Radisson Tristan Radisson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: