We’re using aerospike-rest-gateway as the read path between our AWS Lambda (Node.js) and Aerospike. On June 15, our gateway pods restarted due to routine node maintenance, attempted to pull aerospike/aerospike-rest-gateway:latest from Docker Hub, and received 404. Both pods entered ImagePullBackOff. Our production read path was down for quite afew hours before we identified the cause. The GitHub repo was archived on June 5, but we received no deprecation notice, no Docker Hub deprecation notice, and no announcement on this forum. The images were simply gone.
Questions:
- Is there an official replacement for the REST gateway?
- Is the recommended migration path to switch Lambda to the native Node.js client directly?
- Going forward, can Aerospike post deprecation notices on this forum BEFORE removing artifacts that production systems depend on?
We’ve since self-hosted v2.1.13 built from the official tarball, ) Index of /artifacts/aerospike-rest-gateway ) .. but this was a painful discovery. Other teams using :latest will hit the same thing on their next pod restart.
Please let me know. if I missed some message or community note given earlier. But from what i have seen there are no notices of this.