k8s virtual server vs ingress

[gothub]

I'd like to switch the k8s configuration to use NGINX virtual server routing instead of the ingress resource that we have been using for metadig-engine. This feature has been available since NGINX v1.5.0 (May 2019)

NGINX will still be used as the ingress controller, which will use the virtual server and virtual server route resource to route requests from the main k8s URL to the services running in k8s.

NGINX has stated that it will continue to support ingress resources, but will halt any new development or features for them. All new development is being put into the virtual server and route mechanism.

The components needed to support this are:

• the NGINX ingress controller
  • the manifest files (.yml) will continue to be in the metadig-engine repo
  • the controller will serve both metadig-engine and bookkeeper services
• the virtual server
  • the manifest files for this will be in the metadig-engine repo, under 'nceas-nginx'
• the virtual server route
  • the manifest files for this will be in the bookkeeper repo
  • metadig-engine will have a similar route .yml in the metadig-engine repo

[gothub]

Use of the NGINX Inc. Ingress controller has been dropped in favor of the k8s community NGINX version, see https://github.com/DataONEorg/k8s-cluster/blob/main/control-plane/control-plane.md#ingress-controller for details.