Would it be nice to bundle the upstream CoreDNS version into the k8s-gateway release?

[mstoetzer]

Something like <CoreDNS_UPSTREAM>-<Plugin_VERSION> e.g. image: quay.io/oriedge/k8s_gateway:1.9.1-0.3.0

[networkop]

yeah, I think this is possible. I've never seen this pattern before though. Any other plugins that implement this?

[mstoetzer]

According to https://semver.org/ the CoreDNS version can be interpreted as build version / build number or metadata. Some discussion on this and this

The plus "+" sign that indicates metadata can't be used in Docker tags

[networkop]

We already do that for the binary itself, so it's visible using the version flag

k8s_gateway/cmd/coredns.go

Line 43 in 4693e5c

caddy.AppVersion = fmt.Sprintf("%s+k8s_gateway-%s", coremain.CoreVersion, pluginVersion)

Do you want this only for the image tag?

[mstoetzer]

My idea was to use that version in the image tag. I just wanted to trigger some discussion about that :)

[networkop]

I think it makes sense. Obv, we won't be building the same plugin version for different upstream coredns versions, but we can add an extra tag to an existing image for extra visibility.

[Ornias1993]

Double version is a hell to work with when you update containers using tools like renovate.
It works and can be made to work, but needless double versioning is usually more than a chore than a benefid imho.