Skip to content

feat(operator): Add spec.services.initImage for init container image override#6598

Open
aniketpalu wants to merge 1 commit into
feast-dev:masterfrom
aniketpalu:fix/init-container-image
Open

feat(operator): Add spec.services.initImage for init container image override#6598
aniketpalu wants to merge 1 commit into
feast-dev:masterfrom
aniketpalu:fix/init-container-image

Conversation

@aniketpalu

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Add spec.services.initImage for init container image override.
Init containers (feast-init, feast-apply) previously only used RELATED_IMAGE_FEATURE_SERVER or the compiled-in DefaultImage, ignoring per-FeatureStore custom images. This blocked users with custom Feast images (e.g. Spark-capable) unless an admin patched the operator. Add spec.services.initImage with resolution order:
initImage → RELATED_IMAGE_FEATURE_SERVER → DefaultImage

Which issue(s) this PR fixes:

Checks

  • I've made sure the tests are passing.
  • My commits are signed off (git commit -s)
  • My PR title follows conventional commits format

Testing Strategy

  • Unit tests
  • Integration tests
  • Manual tests
  • Testing is not required for this change

Misc

…override

Init containers (feast-init, feast-apply) previously only used
RELATED_IMAGE_FEATURE_SERVER or the compiled-in DefaultImage, ignoring
per-FeatureStore custom images. This blocked users with custom Feast
images (e.g. Spark-capable) unless an admin patched the operator.
Add spec.services.initImage with resolution order:
  initImage → RELATED_IMAGE_FEATURE_SERVER → DefaultImage

Signed-off-by: Aniket Paluskar <apaluska@redhat.com>
@aniketpalu aniketpalu requested a review from a team as a code owner July 9, 2026 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant