Can't set application version string in K8s charm

Bug #1892216 reported by Kenneth Koski on 2020-08-19
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju
High
Ian Booth

Bug Description

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) wrote :

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.

summary: - Support application version strings in K8s charm
+ Can't set application version string in K8s charm
Ian Booth (wallyworld) wrote :

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.

Changed in juju:
milestone: none → 2.8.3
status: New → Triaged
importance: Undecided → High
assignee: nobody → Ian Booth (wallyworld)
Ian Booth (wallyworld) wrote :
Changed in juju:
milestone: 2.8.3 → 2.8.2
Ian Booth (wallyworld) on 2020-08-21
Changed in juju:
status: Triaged → Fix Committed
Kenneth Koski (knkski) wrote :

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

Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers