Philipp Buehler

That's an OPTIONAL config (go viper) of tink-worker, since all that (as I understand) via ENV and cmdline-ops, it's not needed and not really an error. Basically the worker is...

the sha-references are immutable so that's very weird. cannot try before weekend since @ kubecon

Ah.. that was "fixed" in a newer version -- which just introduced other problems. You can also adapt that in `deploy/compose/generate-tls-certs/ca-{config,csr}.json` if a clock fix is difficult

I see this "every night", too. Some 190 clients across 8 repositories and one or two show this (not always the same ofc). Interestingly with always the exact same timings...