[VAL-105] docker: kube-conformance-{release tag} wrongfully created for validation releases Created: 16/Apr/20  Updated: 21/Apr/20  Resolved: 21/Apr/20

Status: Done
Project: Validation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Medium
Reporter: Alexandru Avadanii Assignee: Alexandru Avadanii
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

kube-conformance is atipical, since instead of '-latest', it is tagged with the actual kube-conformance upstream version (currently v1.16) - so we build and tag [2] every night.

However, for tagged validation releases, the upstream tag is wrongly overwritten by the validation tag (currently 3.0.0), resulting in building and pushing [1].

[1] https://hub.docker.com/layers/akraino/validation/kube-conformance-3.0.0/images/sha256-82f73e593fe2a7d552049c61cf371a911334c83acf0228b62ec40b46e9889337?context=explore

[2] https://hub.docker.com/layers/akraino/validation/kube-conformance-v1.16/images/sha256-f0976d0c2ee3c4062dc0bf7f880620d8ac2a4e04a6e319b45ffec74d0e1004b8?context=explore

 Comments   
Comment by Alexandru Avadanii [ 21/Apr/20 ]

A fix preventing this from happening again has been merged.

Also, the misleading image tags have been removed from Docker hub:

  • akraino/validation:kube-conformance-2.0.0
  • akraino/validation:kube-conformance-amd64-2.0.0
  • akraino/validation:kube-conformance-arm64-2.0.0
  • akraino/validation:kube-conformance-2.0.1
  • akraino/validation:kube-conformance-amd64-2.0.1
  • akraino/validation:kube-conformance-arm64-2.0.1
  • akraino/validation:kube-conformance-3.0.0
  • akraino/validation:kube-conformance-amd64-3.0.0
  • akraino/validation:kube-conformance-arm64-3.0.0
Generated at Sat Feb 10 06:07:21 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.