In managing multiple dgraph instances, it is becoming cumbersome to go inside each docker container and do a backup via /admin/export. Resurrecting this post from @mrjn, Unable to run /admin/export on server via Putty, would it make sense to implement a whitelist feature for /admin/backup?
My specific setup: I’m using docker with user-defined networks. So my app is running one container, and that app accesses the dgraph instance via docker DNS at “dgraph:8080”. When I try to trigger a backup from the app container, the IP recognized by dgraph is 172.19.0.4. I need graph to allow the app container to trigger backups.
In preparing to scale our app, we are planning on learning how to get dgraph up and running on Kubernetes, so we’ll need a solution that works with kubernetes as well - ideally without having to think about specific IP addresses. I’ve seen some activity on Kubernetes support in the dgraph repo…looking forward to trying this out.