Can't set application version string in K8s charm

[Kenneth Koski]

I would like to include upstream versioning information in K8s charms. For example, when a user deploys `cs:~kubeflow-charmers/pipelines-api-110`, they have no way of knowing that the upstream version deployed is `0.2.0`, unless they dig down into the output from `kubectl describe pods/pipelines-api`.

The same is also true for bundles. There's no way for a user to know that they have e.g. Kubeflow 1.0 deployed vs 1.1, all they see is `kubeflow-123`, which doesn't contain that information.

[Kenneth Koski (knkski)]

I was made aware of `hookenv.application_version_set`, but that didn't seem to work.

https://discourse.juju.is/t/hook-tools/1163#heading--application-version-set

I've updated the title to reflect that specific bug.

[Ian Booth (wallyworld)]

I checked the implementation and for k8s charms, the application version is supposed to show the docker image path. However, there's a bug because when the change was done to model the docker image to include username and password as well as path, the code used for juju status wasn't updated.

I think what should happen is that we continue to display docker image path, but is the charm explicitly calls application-version-set, we use that instead.

[Ian Booth (wallyworld)]

https://github.com/juju/juju/pull/11925

[Kenneth Koski (knkski)]

Thanks, this fixed the version issue, but had a side effect where every charm that sets its version shows a scale of `1/0`.