Skip to content

Changed volume uploader pod image pull policy to "Always" #2852

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

luciantin
Copy link
Contributor

Changes

  • 🐛 Fix stale func-utils:v2 image usage by changing imagePullPolicy to "Always"

/kind bug

Fixes #2835

Default image pull policy was "IfNotPresent", therefore the image would be pulled only once, unless manually changed, and builds would not pull new updated images.

Problem described in #2835 (comment).
Solved by changing the image pull policy of the volume-uploader pod only.

As the volume uploader pod runs before any tasks in https://github.com/knative/func/blob/main/pkg/pipelines/tekton/tasks.go, if the tasks use the default func-utils:v2 image, then those pods will also use the latest image.

Release Note

Fixes a bug where remote tekton builds would use a stale image to upload the source directory.

@knative-prow knative-prow bot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 1, 2025
@knative-prow knative-prow bot requested review from dsimansk and jrangelramos June 1, 2025 17:19
@knative-prow knative-prow bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 1, 2025
Copy link

knative-prow bot commented Jun 1, 2025

Hi @luciantin. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Copy link

codecov bot commented Jun 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.47%. Comparing base (01b5c3e) to head (d3e80b1).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2852      +/-   ##
==========================================
+ Coverage   62.66%   63.47%   +0.80%     
==========================================
  Files         127      127              
  Lines       15570    15571       +1     
==========================================
+ Hits         9757     9883     +126     
+ Misses       4900     4746     -154     
- Partials      913      942      +29     
Flag Coverage Δ
e2e-tests 43.62% <100.00%> (+1.47%) ⬆️
integration-tests 49.42% <100.00%> (+1.84%) ⬆️
unit-tests 49.54% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@lkingland
Copy link
Member

Thanks for the contribution!

/ok-to-test

@knative-prow knative-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jun 2, 2025
@matejvasek
Copy link
Contributor

/approve
/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2025
Copy link

knative-prow bot commented Jun 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: luciantin, matejvasek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 2, 2025
@knative-prow knative-prow bot merged commit 33ab476 into knative:main Jun 2, 2025
39 of 41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tekton task "func-buildpacks" prepare/results steps use non-multi-arch bash:5.1.4 image, causing exec format errors on ARM64
3 participants