Update port number to match exposed port from container (#163)

Dockerfile

@@ -146,7 +146,7 @@ RUN chmod +x /workspace/docker/entrypoint.sh
 # Set entrypoint to tini with a custom entrypoint script
 ENTRYPOINT ["/opt/conda/envs/nv_ingest/bin/tini", "--", "/workspace/docker/entrypoint.sh"]
 
-# Start the pipeline and services
+# Start both the core nv-ingest pipeline service and the FastAPI microservice in parallel
 CMD ["sh", "-c", "python /workspace/pipeline.py & uvicorn nv_ingest.main:app --workers 32 --host 0.0.0.0 --port 7670 & wait"]
 
 FROM nv_ingest_install AS development

helm/README.md

@@ -92,15 +92,15 @@ minikube addons enable storage-provisioner-rancher
 
 Jobs are submitted via the `nv-ingest-cli` command. See installation [here](https://github.com/NVIDIA/nv-ingest/tree/main/client)
 
-### Access To Redis
+### Access To NV Ingest API
 
 It is recommended that the end user provide a mechanism for [`Ingress`](https://kubernetes.io/docs/concepts/services-networking/ingress/) for the Redis pod.
 You can test outside of your Kuberenetes cluster by [port-forwarding](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_port-forward/) the Redis pod to your local environment.
 
 Example:
 
 ```bash
-kubectl port-forward -n ${NAMESPACE} nv-ingest-redis-master-0 6379:6379
+kubectl port-forward -n ${NAMESPACE} service/nv-ingest 7670:7670
 ```
 
 ### Executing jobs

helm/templates/deployment.yaml

@@ -132,7 +132,7 @@ spec:
 
           ports:
             - name: http
-              containerPort: {{ .Values.service.port }}
+              containerPort: 7670
               protocol: TCP
           {{- if .Values.livenessProbe.enabled }}
           livenessProbe:

helm/values.yaml

@@ -473,7 +473,7 @@ readinessProbe:
 ## @param service.labels [object] Specifies additional labels to be added to service.
 service:
   type: ClusterIP
-  port: 8000
+  port: 7670
   annotations: {}
   labels: {}
   name: ""  # override the default service name