THREDDS is the only service accessible via http://$(minikube ip).nip.io/thredds

[anikfal]

Hi,
Following the instructions to deploy ESGF using Kubernetes, all services seem to be up and running:

$ kubectl get pods -n esgf-namespace 
NAME                                READY   STATUS    RESTARTS        AGE
esgf-file-server-5bdd6fcb46-8q8h2   1/1     Running   2 (4m18s ago)   75m
esgf-search-69d55ffc84-wgxx6        1/1     Running   2 (4m18s ago)   75m
esgf-solr-llnl-869df9f87d-kg482     1/1     Running   2 (4m17s ago)   75m
esgf-solr-master-785dd78f96-l8h78   1/1     Running   2 (4m17s ago)   75m
esgf-solr-slave-cd4cb856c-7rk5m     1/1     Running   2 (4m17s ago)   75m
esgf-thredds-76f4bc95d-qv8ls        1/1     Running   2 (4m16s ago)   75m

However, only THREDDS can be accessed via https://192.168.49.2.nip.io/thredds.
Other services, especially search cannot be accessed by the same approach (e.g. https://192.168.49.2.nip.io/esg-search), throwing errors as follows:

HTTP Status 404 \u2013 Not Found

Type Status Report

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/8.5.81

---

More information:
It seems the ps command is not found according to the logs of solr pod:

$ kubectl logs esgf-solr-master-785dd78f96-l8h78 -n esgf-namespace 
[info] Running pre-init customisations from /docker-init.d
/usr/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
[info] Running customisations from /docker-init.d/01-init-solr-home.sh
[info] Running customisations from /docker-init.d/02-init-esgf-cores.sh
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/opt/solr/bin/solr: line 1618: ps: command not found