Open anikfal opened 4 hours ago
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
All services show endpoint
/thredds esgf-thredds:8080 (10.244.0.228:8080)
/thredds/fileServer esgf-file-server:8080 (10.244.0.224:8080)
/solr/aggregations/replication esgf-solr-slave:8983 (10.244.0.226:8983)
/solr/datasets/replication esgf-solr-slave:8983 (10.244.0.226:8983)
/solr/files/replication esgf-solr-slave:8983 (10.244.0.226:8983)
/esg-search esgf-search:8080 (10.244.0.227:8080)
esg-search last state is terminated with reason error and exit code 143
Last State: Terminated
Reason: Error
Exit Code: 143
Started: Mon, 14 Oct 2024 11:46:31 +0200
Finished: Mon, 14 Oct 2024 16:31:42 +0200
If you post informastion as per the template of a new bug report, then readers get the data that can be analyzed. But you have posted info as per your own assumptions so there is no data to analyze
nip.io dns names are good for dns but no data is provided as to the validity of the cert. I would never create a cert for nip.io dns names
Unexpected error validating SSL certificate "default/esgf-hostcert" for server "192.168.49.2.nip.io": x509: certificate relies on legacy Common Name field, use SANs instead
/kind support
--watch-ingress-without-class=true
whatever word applies because there is no curl command with -iv and its response, posted here, to know exactly what is wrong
Brief Error Report:
The
esgf-thredds
service is available athttp://$(minikube ip).nip.io/thredds
. However, other services (e.g.https://192.168.49.2.nip.io/esg-search
) cannot be accessed, throwing Apache Tomcat error (HTTP Status 404 – Not Found
).Logging information:
1)
$ kubectl get all
2)
$ kubectl describe ingress esgf-ingress
3)
$ kubectl logs -n ingress-nginx ingress-nginx-controller-bc57996ff-zkvj9
4)
$ kubectl describe pod ingress-nginx-controller-bc57996ff-zkvj9 -n ingress-nginx
5)
$ kubectl describe pod esgf-search-599b64bb5f-j2mdn