GKE Marketplace Versioning / Tracks
TL;DR After below discussion, we will base the Track ID on the Major & Major.Minor of the appVersion
value in Chart.yml
from the gitlab
submodule (which is of charts/gitlab)
Discussion on track matching chart or application version
In #735 (closed), we discussed the handling of versions via Track ID & the relation of the track to the container versions.
I am suggesting that we take the Track ID from the version of charts/gitlab via Chart.yml, and thus tie the GKE Marketplace versioning to the chart version, rather than to the version of GitLab application code itself.
The "track" and version in the marketplace is controlled by the tag on the deployer container, not the individual application containers in schema.yml
. We would tag the deployer as 1.2
and 1.2.x
, pushing both tags.
Then, using the container versions as defined by each chart's image.{repository,tag}
(in #911 (closed)), a user will be able to see Container images
on the right side of the marketplace which clearly state which version of each container is in use. This would display v11.4.x
for all of the Rails related images, 3.26
for the Redis, etc.
Relates to #911 (closed) and #912 (closed)
This is what the Container images
list looks like in the existing entry, on Track "11"