Skip to content

Bootstrap sensor upgrade test#19291

Closed
msugakov wants to merge 4 commits intomasterfrom
misha/move-upgrade-sensor-test-to-gha
Closed

Bootstrap sensor upgrade test#19291
msugakov wants to merge 4 commits intomasterfrom
misha/move-upgrade-sensor-test-to-gha

Conversation

@msugakov
Copy link
Contributor

@msugakov msugakov commented Mar 4, 2026

Try creating and destroying GKE cluster

Description

change me!

User-facing documentation

Testing and quality

  • the change is production ready: the change is GA, or otherwise the functionality is gated by a feature flag
  • CI results are inspected

Automated testing

  • added unit tests
  • added e2e tests
  • added regression tests
  • added compatibility tests
  • modified existing tests

How I validated my change

change me!

Try creating and destroying GKE cluster
@openshift-ci
Copy link

openshift-ci bot commented Mar 4, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • Consider tightening the workflow triggers (e.g., limiting push to specific branches or using a required label on PRs) to avoid unintentionally creating GKE clusters on every push/PR where this test isn’t actually needed.
  • It may be useful to set an explicit timeout-minutes on the upgrade-test job to ensure that leaked or hung runs don’t keep GKE clusters alive longer than expected.
  • Since INFRA_TOKEN is exposed as a job-level env var, consider passing it only to the specific create-cluster/infractl steps that require it to reduce the scope of the secret.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider tightening the workflow triggers (e.g., limiting `push` to specific branches or using a required label on PRs) to avoid unintentionally creating GKE clusters on every push/PR where this test isn’t actually needed.
- It may be useful to set an explicit `timeout-minutes` on the `upgrade-test` job to ensure that leaked or hung runs don’t keep GKE clusters alive longer than expected.
- Since `INFRA_TOKEN` is exposed as a job-level env var, consider passing it only to the specific `create-cluster`/`infractl` steps that require it to reduce the scope of the secret.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@rhacs-bot
Copy link
Contributor

rhacs-bot commented Mar 4, 2026

Images are ready for the commit at a48d0bd.

To use with deploy scripts, first export MAIN_IMAGE_TAG=4.11.x-238-ga48d0bd468.

@codecov
Copy link

codecov bot commented Mar 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 49.62%. Comparing base (141b82d) to head (a48d0bd).
⚠️ Report is 18 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #19291   +/-   ##
=======================================
  Coverage   49.62%   49.62%           
=======================================
  Files        2680     2680           
  Lines      202195   202214   +19     
=======================================
+ Hits       100332   100346   +14     
- Misses      94386    94391    +5     
  Partials     7477     7477           
Flag Coverage Δ
go-unit-tests 49.62% <ø> (+<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:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@msugakov
Copy link
Contributor Author

msugakov commented Mar 5, 2026

I'll more likely proceed with #19303

@msugakov msugakov closed this Mar 5, 2026
@msugakov msugakov deleted the misha/move-upgrade-sensor-test-to-gha branch March 5, 2026 17:46
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.

2 participants