When rebuilding a cluster using the deployment guide, @rconway hit the following pod errors for data-access:
$ kubectl -n data-access get pod | grep -i error
eoapi-maps-plugin-sync-29143550-2lhfl 0/1 Error 0 106s
eoapi-maps-plugin-sync-29143550-trnx9 0/1 Error 0 95s
With the logs...
$ kubectl -n data-access logs eoapi-maps-plugin-sync-29143550-2lhfl
Traceback (most recent call last):
File "/emp/scripts/sync.py", line 290, in <module>
main()
File "/emp/scripts/sync.py", line 174, in main
stac_collections, pygeoapi_resources = get_data(
File "/emp/scripts/sync.py", line 109, in get_data
r.raise_for_status()
File "/usr/local/lib/python3.10/dist-packages/requests/models.py", line 1024, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://maps.verify.eoepca.org/admin/config/resources
The maps endpoint is up...
$ curl -I https://maps.verify.eoepca.org/
HTTP/2 200
content-type: application/json
content-length: 2731
date: Fri, 30 May 2025 13:54:22 GMT
x-powered-by: pygeoapi 0.19.0
content-language: en-US
server: APISIX
access-control-allow-origin: *
access-control-allow-methods: *
access-control-max-age: 5
access-control-allow-headers: *
But not the path expected...
$ curl https://maps.verify.eoepca.org/admin/config/resources
{"error_msg":"404 Route Not Found"}
When rebuilding a cluster using the deployment guide, @rconway hit the following pod errors for data-access:
The maps endpoint is up...
But not the path expected...