Fix reciter-consumer API

[paulalbert1]

Background

This code should retrieve articles from outside the WCM network. It was built primarily so that WCM's Software Development Services (Charles Hydo, in particular) could retrieve articles and populate them in our Drupal installations, which are externally hosted.

curl --location --request GET 'https://reciter-consumer.weill.cornell.edu/reciter/article-retrieval/by/uid?uid=ccole' \
--header 'api-key: [RECITER CONSUMER API KEY]'

The basic goal is to make the "reciter-prod" deployment accessible via the reciter-consumer.weill.cornell.edu domain.

Requirements

AFAIK, one or both of these steps are needed:

1. Carlos created a new certificate for reciter-consumer, but he didn't attach it to the load balancer. (The use of a certificate ensures that the above command will work without having to use the -k flag.) I have the correct load balancer.

2. Update the ingress for reciter-prod. We already have ingress-nginx installed in our "reciter" cluster. We can create an Ingress resource that points to the reciter-prod service. This will allow us to access the service using a domain name. Once the Ingress resource is set up, you can point your domain to the Ingress Controller's IP or DNS name.

3. Update the load balancer.