Skip to content

Use consistent calicoImage field name for combined calico image#4838

Merged
caseydavenport merged 2 commits into
tigera:masterfrom
caseydavenport:casey-combined-image-cleanup
May 20, 2026
Merged

Use consistent calicoImage field name for combined calico image#4838
caseydavenport merged 2 commits into
tigera:masterfrom
caseydavenport:casey-combined-image-cleanup

Conversation

@caseydavenport
Copy link
Copy Markdown
Member

Follow-up cleanup after #4608.

Renames every render struct field that holds the combined calico/calico image reference to calicoImage, so it's obvious at the use site which image is being pulled. Also collapses a few redundant fields that all aliased the same combined image:

  • compliance.go: 4 fields (snapshotterImage, serverImage, controllerImage, reporterImage) -> 1
  • manager.go: 2 fields (voltronImage, uiAPIsImage) -> 1
  • apiserver.go: 3 fields (apiServerImage, queryServerImage, l7AdmissionControllerImage) -> 1
  • csi.go: 2 fields (csiImage, csiRegistrarImage) -> 1
  • node.go: 2 fields (cniImage, flexvolImage) -> 1

Pure rename / consolidation, no functional change. Render and controller UTs pass locally.

@caseydavenport caseydavenport merged commit f3ca399 into tigera:master May 20, 2026
6 checks passed
@caseydavenport caseydavenport deleted the casey-combined-image-cleanup branch May 20, 2026 22:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants