Skip to content

Add Installation.Spec.ImagePullPolicy#4797

Merged
caseydavenport merged 3 commits into
tigera:masterfrom
caseydavenport:casey-image-pull-policy
May 13, 2026
Merged

Add Installation.Spec.ImagePullPolicy#4797
caseydavenport merged 3 commits into
tigera:masterfrom
caseydavenport:casey-image-pull-policy

Conversation

@caseydavenport
Copy link
Copy Markdown
Member

Adds an imagePullPolicy field to the Installation spec. When set, the operator applies it to every container in every pod it renders, overriding any default the renderers set themselves. This is for air-gapped clusters where images are pre-loaded onto nodes and shouldn't get pulled from a remote registry.

The pull policy is also now applied to init containers, which the central pass was previously missing.

Fixes projectcalico/calico#7107.

Added `Installation.Spec.ImagePullPolicy` for overriding the pull policy of all operator-managed pods, useful in air-gapped clusters.

Comment thread pkg/controller/utils/component.go Outdated
Comment thread pkg/controller/utils/component.go Outdated
When set, the configured pull policy is applied to every container in pods
rendered by the operator, overriding any default the renderer would otherwise
set. Useful in air-gapped clusters where images are pre-loaded onto nodes.
@caseydavenport caseydavenport force-pushed the casey-image-pull-policy branch from ec6d4f8 to 82ccb8a Compare May 13, 2026 18:02
@caseydavenport caseydavenport merged commit 1b6d604 into tigera:master May 13, 2026
5 checks passed
@caseydavenport caseydavenport deleted the casey-image-pull-policy branch May 13, 2026 18:27
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.

Allow specifying the Helm Chart's imagePullPolicy in values.yaml

3 participants