adding support to pass cred that enables scale-from-zero test in hype… - #72805
Merged
openshift-merge-bot[bot] merged 2 commits intoJan 19, 2026
Merged
Conversation
jhjaggars
marked this pull request as draft
December 18, 2025 17:20
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
jhjaggars
force-pushed
the
scale-from-zero-hypershift-test
branch
from
January 12, 2026 17:49
def39c1 to
f52a90f
Compare
Contributor
Author
|
/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws |
Contributor
|
@jhjaggars: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
jhjaggars
marked this pull request as ready for review
January 13, 2026 14:52
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
Contributor
Author
|
/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws |
Contributor
|
@jhjaggars: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws |
Contributor
|
@jhjaggars: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws |
Contributor
|
@jhjaggars: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
jhjaggars
force-pushed
the
scale-from-zero-hypershift-test
branch
from
January 14, 2026 23:22
acbab7f to
6398d56
Compare
Contributor
Author
|
/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws |
Contributor
|
@jhjaggars: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Co-Authored-By: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>
jhjaggars
force-pushed
the
scale-from-zero-hypershift-test
branch
from
January 15, 2026 13:25
6398d56 to
995dd38
Compare
Contributor
|
[REHEARSALNOTIFIER]
A total of 899 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
Contributor
Author
|
/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws |
Contributor
|
@jhjaggars: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
4 tasks
Contributor
|
/lgtm |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhjaggars, LiangquanLi930 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
Contributor
|
/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws |
Contributor
|
@LiangquanLi930: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Contributor
|
@jhjaggars: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
Contributor
|
rehearsal failed due to flake, but HO install worked with new flags /pj-rehearse ack |
Contributor
|
@sjenning: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
openshift-merge-bot
Bot
merged commit Jan 19, 2026
aa839bd
into
openshift:master
10 of 11 checks passed
dhensel-rh
pushed a commit
to dhensel-rh/release
that referenced
this pull request
Feb 19, 2026
openshift#72805) * adding support to pass cred that enables scale-from-zero test in hypershift * Add scale-from-zero configuration for e2e-aws Co-Authored-By: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>
3 tasks
openshift-merge-bot Bot
pushed a commit
that referenced
this pull request
Jul 1, 2026
…<= 4.22 (#81259) * hypershift: gate scale-from-zero flags behind ENABLE_SCALE_FROM_ZERO toggle PR #72805 added --scale-from-zero-provider and --scale-from-zero-creds unconditionally to the hypershift install step. This broke upgrade-hypershift-operator jobs on pre-4.22 branches because those release-tagged operator images lack the flags. Move the flags behind an ENABLE_SCALE_FROM_ZERO env var (default true) and set it to false for the upgrade-hypershift-operator test in 4.19, 4.20, and 4.21 configs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: move scale-from-zero flags inside AWS case block Address review feedback: keep AWS-specific --scale-from-zero-provider and --scale-from-zero-creds inside the AWS case block rather than in EXTRA_ARGS, which leaks into Azure/GCP/other install paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: upgrade test should upgrade to the PR-built operator image The upgrade-hypershift-operator test on release branches <= 4.22 was upgrading to hypershift-operator:latest (main) instead of the version-tagged image built from the PR. Override CI_HYPERSHIFT_OPERATOR to point to the PR-built hypershift-operator-4XX image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> --------- Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
krisnababu
pushed a commit
to oharan2/release
that referenced
this pull request
Jul 3, 2026
…<= 4.22 (openshift#81259) * hypershift: gate scale-from-zero flags behind ENABLE_SCALE_FROM_ZERO toggle PR openshift#72805 added --scale-from-zero-provider and --scale-from-zero-creds unconditionally to the hypershift install step. This broke upgrade-hypershift-operator jobs on pre-4.22 branches because those release-tagged operator images lack the flags. Move the flags behind an ENABLE_SCALE_FROM_ZERO env var (default true) and set it to false for the upgrade-hypershift-operator test in 4.19, 4.20, and 4.21 configs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: move scale-from-zero flags inside AWS case block Address review feedback: keep AWS-specific --scale-from-zero-provider and --scale-from-zero-creds inside the AWS case block rather than in EXTRA_ARGS, which leaks into Azure/GCP/other install paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: upgrade test should upgrade to the PR-built operator image The upgrade-hypershift-operator test on release branches <= 4.22 was upgrading to hypershift-operator:latest (main) instead of the version-tagged image built from the PR. Override CI_HYPERSHIFT_OPERATOR to point to the PR-built hypershift-operator-4XX image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> --------- Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
andrej1991
pushed a commit
to andrej1991/release
that referenced
this pull request
Jul 6, 2026
…<= 4.22 (openshift#81259) * hypershift: gate scale-from-zero flags behind ENABLE_SCALE_FROM_ZERO toggle PR openshift#72805 added --scale-from-zero-provider and --scale-from-zero-creds unconditionally to the hypershift install step. This broke upgrade-hypershift-operator jobs on pre-4.22 branches because those release-tagged operator images lack the flags. Move the flags behind an ENABLE_SCALE_FROM_ZERO env var (default true) and set it to false for the upgrade-hypershift-operator test in 4.19, 4.20, and 4.21 configs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: move scale-from-zero flags inside AWS case block Address review feedback: keep AWS-specific --scale-from-zero-provider and --scale-from-zero-creds inside the AWS case block rather than in EXTRA_ARGS, which leaks into Azure/GCP/other install paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: upgrade test should upgrade to the PR-built operator image The upgrade-hypershift-operator test on release branches <= 4.22 was upgrading to hypershift-operator:latest (main) instead of the version-tagged image built from the PR. Override CI_HYPERSHIFT_OPERATOR to point to the PR-built hypershift-operator-4XX image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> --------- Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
smulje
pushed a commit
to smulje/release
that referenced
this pull request
Jul 9, 2026
…<= 4.22 (openshift#81259) * hypershift: gate scale-from-zero flags behind ENABLE_SCALE_FROM_ZERO toggle PR openshift#72805 added --scale-from-zero-provider and --scale-from-zero-creds unconditionally to the hypershift install step. This broke upgrade-hypershift-operator jobs on pre-4.22 branches because those release-tagged operator images lack the flags. Move the flags behind an ENABLE_SCALE_FROM_ZERO env var (default true) and set it to false for the upgrade-hypershift-operator test in 4.19, 4.20, and 4.21 configs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: move scale-from-zero flags inside AWS case block Address review feedback: keep AWS-specific --scale-from-zero-provider and --scale-from-zero-creds inside the AWS case block rather than in EXTRA_ARGS, which leaks into Azure/GCP/other install paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: upgrade test should upgrade to the PR-built operator image The upgrade-hypershift-operator test on release branches <= 4.22 was upgrading to hypershift-operator:latest (main) instead of the version-tagged image built from the PR. Override CI_HYPERSHIFT_OPERATOR to point to the PR-built hypershift-operator-4XX image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> --------- Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
SachinNinganure
pushed a commit
to SachinNinganure/release
that referenced
this pull request
Jul 20, 2026
…<= 4.22 (openshift#81259) * hypershift: gate scale-from-zero flags behind ENABLE_SCALE_FROM_ZERO toggle PR openshift#72805 added --scale-from-zero-provider and --scale-from-zero-creds unconditionally to the hypershift install step. This broke upgrade-hypershift-operator jobs on pre-4.22 branches because those release-tagged operator images lack the flags. Move the flags behind an ENABLE_SCALE_FROM_ZERO env var (default true) and set it to false for the upgrade-hypershift-operator test in 4.19, 4.20, and 4.21 configs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: move scale-from-zero flags inside AWS case block Address review feedback: keep AWS-specific --scale-from-zero-provider and --scale-from-zero-creds inside the AWS case block rather than in EXTRA_ARGS, which leaks into Azure/GCP/other install paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: upgrade test should upgrade to the PR-built operator image The upgrade-hypershift-operator test on release branches <= 4.22 was upgrading to hypershift-operator:latest (main) instead of the version-tagged image built from the PR. Override CI_HYPERSHIFT_OPERATOR to point to the PR-built hypershift-operator-4XX image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> --------- Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
amogh-redhat
pushed a commit
to amogh-redhat/release
that referenced
this pull request
Aug 5, 2026
![openshift-prow[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…<= 4.22 (openshift#81259) * hypershift: gate scale-from-zero flags behind ENABLE_SCALE_FROM_ZERO toggle PR openshift#72805 added --scale-from-zero-provider and --scale-from-zero-creds unconditionally to the hypershift install step. This broke upgrade-hypershift-operator jobs on pre-4.22 branches because those release-tagged operator images lack the flags. Move the flags behind an ENABLE_SCALE_FROM_ZERO env var (default true) and set it to false for the upgrade-hypershift-operator test in 4.19, 4.20, and 4.21 configs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: move scale-from-zero flags inside AWS case block Address review feedback: keep AWS-specific --scale-from-zero-provider and --scale-from-zero-creds inside the AWS case block rather than in EXTRA_ARGS, which leaks into Azure/GCP/other install paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: upgrade test should upgrade to the PR-built operator image The upgrade-hypershift-operator test on release branches <= 4.22 was upgrading to hypershift-operator:latest (main) instead of the version-tagged image built from the PR. Override CI_HYPERSHIFT_OPERATOR to point to the PR-built hypershift-operator-4XX image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> --------- Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
TimurMP
pushed a commit
to TimurMP/release
that referenced
this pull request
Sep 5, 2026
…<= 4.22 (openshift#81259) * hypershift: gate scale-from-zero flags behind ENABLE_SCALE_FROM_ZERO toggle PR openshift#72805 added --scale-from-zero-provider and --scale-from-zero-creds unconditionally to the hypershift install step. This broke upgrade-hypershift-operator jobs on pre-4.22 branches because those release-tagged operator images lack the flags. Move the flags behind an ENABLE_SCALE_FROM_ZERO env var (default true) and set it to false for the upgrade-hypershift-operator test in 4.19, 4.20, and 4.21 configs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: move scale-from-zero flags inside AWS case block Address review feedback: keep AWS-specific --scale-from-zero-provider and --scale-from-zero-creds inside the AWS case block rather than in EXTRA_ARGS, which leaks into Azure/GCP/other install paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> * hypershift: upgrade test should upgrade to the PR-built operator image The upgrade-hypershift-operator test on release branches <= 4.22 was upgrading to hypershift-operator:latest (main) instead of the version-tagged image built from the PR. Override CI_HYPERSHIFT_OPERATOR to point to the PR-built hypershift-operator-4XX image. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> --------- Signed-off-by: Ahmed Abdalla <aabdelre@redhat.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…rshift