bogus user-agent in k8s API requests

[Paul Collins]

While examining the audit logs on one of our k8s clusters, I noticed the user-agent for our 2.8.0 controllers is as follows:

jujud/v0.0.0 (linux/amd64) kubernetes/$Format

"v0.0.0" looks obviously wrong.

"kubernetes/$Format" also looks strange, but perhaps it's expected?

[Pen Gale (pengale)]

Looks like something is not being completely formatted.

I suspect that this is just a matter of a bit of code spelunking, followed by passing a value or two to a formatter, so tagging as bitesized.

[timeless (timeless)]

Sorry, just realized you have two items in play.

The `v0.0.0` is definitely jujud's fault.

The `$Format` bit appears to be the Kubernetes server's fault.
I'm pretty sure that the code in question is kubernetes itself logging the request is this:
https://github.com/kubernetes/client-go/blob/4154d814be868b4bcf610332288a913fca8f4dc1/rest/config.go#L495

There are lots of reports of the Kubernetes side, e.g.:
https://github.com/kubernetes/kops/issues/9698
https://github.com/cert-manager/cert-manager/issues/1479

I've personally seen it w/ ArgoCD and K9s as the clients.

It seems like you meant to leave this focused on the juju side.