Christian Simon

There still are some problems with the ubuntu test: - https://jetstack-build-infra.appspot.com/build/jetstack-logs/pr-logs/pull/jetstack_tarmak/570/tarmak-puppet-module-tarmak-acceptance-1-10-ubuntu/152/ Seems like the keyserver is sometimes not available

I think the correct input should be: > `2019-03-05 10:51:10` Where is the `24 hours ago` coming from?

Can you have a look at this: https://twitter.com/opsgoodness/status/1098266699382620160 Don't want to get into that trouble with the update. The performance fixes seemed to have happened with 1.5.0 /assign @MattiasGees /unassign

I would argue it makes sense to also allow multiple masters

Would be great to get that updated an merged @kragniz

/assign @MattiasGees /unassign

What I am doing server side (I am using the rest-server): https://gist.github.com/simonswine/494e27e9aa38647a7cb735cc3ccc9da0 This will export metrics like that to node_exporter's [textfile collector](https://github.com/prometheus/node_exporter#textfile-collector): ``` restic_latest_snapshot_time_seconds{repository="/opt/backup/restic/backup-a"} 1536563994 restic_latest_snapshot_time_seconds{repository="/opt/backup/restic/backup-b"} 1536563361 restic_repository_size_bytes{repository="/opt/backup/restic/backup-a"} 3822400 restic_repository_size_bytes{repository="/opt/backup/restic/backup-b"}...

We had the idea to encode the timestamp into the ID e.g. using ULID

This is how it looks like 

I think we already do that, can you double check if I am getting this right, but this should do what I think you want: ```yaml phlare: securityContext: runAsNonRoot: true...