feat: Allow using a pull thru docker cache with the imagepolicy schedule

[ekampf]

Related Tickets & Documents

• Issue: Using a pull-thru docker cache with the imagePolicy schedule feature? #427

Changes

Changes how DockerhubVersionPolicyProvider (used to fetch latest tag from dockerhub) behaves - when looking for new tags we always check the official twingate repo (twingate/connector) and we use the repository value from the CRD when referncing it in the pod.

So for example given this connector yaml:

apiVersion: twingate.com/v1beta
kind: TwingateConnector
metadata:
  name: my-connector-auto-updating-image
spec:
  imagePolicy:
    provider: "dockerhub"
    schedule: "0 0 * * *"
    repository: my-private-repo/twingate-connector
    version: "^1.0.0"
  podExtra:
    imagePullSecrets:
      - name: my-secret

The code will query twingate/connector on dockerhub to get the latest tags and then when creating the pod set the image to be my-private-repo/twingate-connector:<latest tag from dockerhub>

[linear]

OSS-48 Using a pull-thru docker cache with the imagePolicy schedule feature?

[coveralls]

Pull Request Test Coverage Report for Build 12262932885

Details

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 98.394%

---

Totals
Change from base Build 12205215703:	0.0%
Covered Lines:	1015
Relevant Lines:	1022

---

💛 - Coveralls

[liorr]

GTM