virtual host options

The argoci docs have a section on how to configure an ingress controller. We should add a Contour section to show users who want to use Contour, what setup needs done.

https://argoproj.github.io/argo-cd/operator-manual/ingress/

Summary

Migrate CustomResourceDefinition to apiextensions.k8s.io/v1 as apiextensions.k8s.io/v1beta1 is deprecated

`CustomResourceDefinition` represents a resource that should be exposed on the API server. Its name MUST
be in the format .spec.name>..spec.group>.
Deprecated in v1.16, planned for removal in v1.19. Use apiextensions.k8s.io/v1 CustomResourceDefinition instead.
`

Use heptio/workgroup to improve handling of the multiple goroutines that are spawned in each of the discoverers. This will also help us to bubble up errors to main, and handle them appropriately.

An example of this is #224. We wanted to handle the case where re-auth failed 3 times, but there was no good way of bubbling up the error to main.go. We could make reconciler.Run return an error to bub

Current State:
The UI section of the CONTRIBUTING.md is somewhat uninspiring.

Desired State:

1. The contributing to UI section could use a screenshot of the Meshery UI
2. In addition to a screenshot in this section, the README should list Billboardjs as on one of the frontend technologies in use.

Description

Currently, the following page on the Resources section on the layer5-ng site points to a 404 error:

Service Mesh Workshops

Migrate the content from the Layer5.io site. The data can be sourced from the following page on the [layer5.io](https://layer5.io

This is an optimization to reduce the time it takes to build/deploy YAStack.

Compilation of YAStack can be optimized by pre-compiling source code that does not depend on DPDK. This can help build the image faster since now only DPDK and dependent code will have to be compiled.

Ref the Issue

List of filters