0

I have noticed that various calico-related images (like https://hub.docker.com/r/calico/ctl/tags or https://hub.docker.com/r/calico/typha/tags) produce 2 types of tags:

  1. Simple version tags, like v3.26.1
  2. Related longer tags like v3.26.1-3-g4073a1bc4827

Since the longer tags follow after the main tag, and have some increasing numbering sequence, I assume these are patch-releases of the same version, which bundle newer underlying images (is this correct understanding)?

Consequently I wanted to use such newer image in my tigera-operator helm deployment. While I was able to pass in additional image/tag info for calicoctl and tigeraOperator images, I did not find a way how to tell it to use corresponding patch-version of calico/typha. Is there some way do do that? Or am I making some wrong assumptions and trying to do wrong thing?

Michal
  • 1,262
  • 1
  • 12
  • 22

0 Answers0