An indicator is needed for project types that require a push registry

[eharris369]

The IDEs need to let the user know when a push registry is required for their project. Currently we are doing the following:

1. On create project the template list has the styles (except for Codewind templates) so if there is no style we assume Codewind style and that a push registry is needed.
2. On add existing project there is no style in the project type listing or in the validation result so the IDEs are looking at the project type id. If it is not appsodyExtension and not odo, Codewind is assumed and so a push registry required. If new extensions are added then this will be broken.

Something more explicit and reliable is needed such as "pushRegistryRequired" on the project type listing.

[tobespc]

one thing we could look at is having our own docker registry that we could use unless overridden by the user

[johnmcollier]

Bundling our own docker registry brings a couple of challenges such that I wouldn't want it to be default functionality:

• Unless using publicly signed certificates, in order to pull from the registry, each Kubernetes worker node needs to have the registry's hostname whitelisted, and then be restarted.
  • This isn't possible on some managed Kubes like IKS, GKE, or OpenShift Online
• Storage requirements: Docker registries require a lot of storage, due to the amount of space that Docker images take up. Red Hat recommends at least 60GB of storage for just testing Quay

[jcockbain]

/assign