I don’t think it’s a Kubernetes issue. The backups are small because Dgraph is instructed to only backup up to a timestamp that is barely greater than the timestamp of the last backup.
I talked to Manish (our CEO) about this problem. He said it’s indeed weird that the timestamps are this way.
Could you try to run some backups again (in an empty bucket)? If you run into the same issue, run a query (any valid query should work) right after the backup and share the manifest of that backup (and the backup before that if it exists) and the result of this query (we only really need the timestamp that is included with the query results).
If binary backups are working fine and you ran the query close enough to the end of the backup, then the timestamp of the query and the latest backup should be about the same (unless you have a a lot of mutations coming in between the two points in time).
Thanks.