After completion of https://github.com/devfile/api/issues/1520 we need to sync the way the Operator and the Helm chart deployments handle a missing Ingress domain. With the new changes to the Operator if an Ingress domain is not entered the creation of that resource is skipped and a log is output to communicate why it was skipped. Additionally, the fqdn is then set to http://localhost:8080 as a default as without an Ingress it won't be communicating outside of the cluster.
Which area/kind this issue is related to?
/area registry
Issue Description
After completion of https://github.com/devfile/api/issues/1520 we need to sync the way the Operator and the Helm chart deployments handle a missing Ingress domain. With the new changes to the Operator if an Ingress domain is not entered the creation of that resource is skipped and a log is output to communicate why it was skipped. Additionally, the
fqdn
is then set tohttp://localhost:8080
as a default as without an Ingress it won't be communicating outside of the cluster.Changes made to the operator can be found here: https://github.com/devfile/registry-operator/pull/89
Acceptance Criteria