Parity doesn't seem to work out of the box with Kubernetes volumes?

[onpaws]

• Parity Ethereum version: 2.5.0
• Operating system: Kubernetes/Linux
• Installation: Docker image: parity/parity:v2.5.0
• Fully synchronized: n/a - this is a crash on startup
• Network: kovan
• Restarted: yes

Steps to Reproduce

1. Provision a Kubernetes cluster
2. Apply the following manifest, which is the same as @ddorgan's but with a version bump
   kubectl apply -f https://gist.github.com/onpaws/eab481b9c237f19db2330d14682a8025

Expected:
Parity runs and we see the usual logs

2019-05-11 10:04:12 UTC Syncing snapshot 2259/3074 #0 23/25 peers 8 KiB chain 513 KiB db 0 bytes queue 15 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2019-05-11 10:04:17 UTC Syncing snapshot 2259/3074 #0 23/25 peers 8 KiB chain 513 KiB db 0 bytes queue 15 KiB sync RPC: 0 conn, 0 req/s, 0 µs

Actual:
Error on startup

Error upgrading parity data: CannotCreateConfigPath(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })

Possibly relevant previous discussion:
#9689 seems to have broken Kubernetes, #9834 purports to have fixed it, but for me using v2.5.0 off the public Docker hub is still broken.

Seems @MicahZoltu and @5chdn also have been impacted, may be related but perhaps not Kubes-specific in their case.

What do you think I should do?

[onpaws]

@fubhy seems you're also using Kubernetes for Parity - if you have a working manifest or some tip you could share, I'd be grateful :)

[onpaws]

Seems like Kubernetes randomizes the UID/GID, which seems to breaks this.
Manually setting the manifest to match the UID/GID of the parity user (which is 1000:1000) fixed it.
Working manifest

If there's some kind of docs repo, I'd be happy to drop in a note. Or whatever place is likely to be seen by future users.