Create devfile for devfile registry deployments

[michael-valdron]

Which area this feature is related to?

/area registry
/area releng

Which functionality do you think we should add?

Why is this needed? Is your feature request related to a problem?

Create a devfile for making deployments of our devfile registries to devfile adopted platforms such as Red Hat Trusted Application Pipeline.

Detailed description:

Currently our community devfile registry is using a OpenShift template for deployment on our dedicated hosting environment. It would be great to have a outerloop devfile with resource deployment specs under the source repository to allow deployments using devfile consumers. In addition, this could also give more options of deployments to those wanting to deploy to their own Kubernetes or OpenShift environments.

Describe the solution you'd like

• Create a devfile which defines the deployment layout for the devfile registry

• Convert existing OpenShift template into compatible deployment spec which can be referenced by the devfile or independently used with other methods

• Make any necessary modifications to scripts

• Update documentation to describe these changes

• Add tests for at least the existing platforms

Apply both tasks for the community devfile registry and the product devfile registry.

Describe alternatives you've considered

Alternatively, we can do one of the following:

1. Use existing deployment template and handle other components using existing methods
2. Convert the existing deployment template to be compatible with more deployment methods without a devfile
   1. Still needs to handle other components using existing methods

Additional context

[michael-valdron]

Changing priority to blocker as it is blocking changes in the deployment setup of the community devfile registry.

[michael-valdron]

Using inline for openshift components to inplace variables. Support for passing OpenShift template parameters in devfiles would simplify this step.

[michael-valdron]

kubernetes components defines the deployment neutral resources and k8s ingress. openshift component continues to define OpenShift Route resource.

This will let us deploy to OpenShift and Kubernetes using common specs.

Using inline for openshift components to inplace variables.

Now using separated resources files with variable references.

[michael-valdron]

Created odo v3 deployment check, currently investigating the following error message experienced with odo in GitHub workflow:

✗  failed to create service(s) associated with the component: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "[https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s](https://ingress-nginx-controller-admission.ingress-nginx.svc/networking/v1/ingresses?timeout=10s)": dial tcp 10.106.217.105:443: connect: connection refused

[michael-valdron]

Created odo v3 deployment check, currently investigating the following error message experienced with odo in GitHub workflow:

✗  failed to create service(s) associated with the component: Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "[https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s](https://ingress-nginx-controller-admission.ingress-nginx.svc/networking/v1/ingresses?timeout=10s)": dial tcp 10.106.217.105:443: connect: connection refused

Error was caused by the ingress controller not being ready before odo deploy was executed, this problem was solved by including the following before executing odo deploy to wait for the ingress controller to be ready:

kubectl wait pods -l app.kubernetes.io/name=ingress-nginx,app.kubernetes.io/component=controller --namespace ingress-nginx --for=condition=Ready --timeout=600s

[michael-valdron]

Devfile confirmed compatiblity with odo v3 and ODC:

[michael-valdron]

PR ready for review: devfile/registry#256