Skip to content

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Oct 16, 2025

Some feature-gates are mutually exclusive, and we need to ensure that those feature-gates are not simultaneously enabled. In some cames, we need to disable upstream flags all the time (e.g. WebhookOperatorCertManager).

This defines a function for each downstream feature-gate that defines how upstream feature-gate flags and arguments should be generated based whether that downstream feature-gate is enabled or disabled. Because these are functions that provides Helm values, they no longer need to be separated along OperatorController and Catalogd lines; the functions determine where the Helm parameters are set.

Added unit tests, mostly written by Claude Code

Assisted-by: Claude Code

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 16, 2025

@tmshort: This pull request references OPRUN-4207 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

Some feature-gates are mutually exclusive, and we need to ensure that those feature-gates are not simultaneously enabled. In some cames, we need to disable upstream flags all the time (e.g. WebhookOperatorCertManager).

This defines a function for each downstream feature-gate that defines how upstream feature-gate flags and arguments should be generated based whether that downstream feature-gate is enabled or disabled. Because these are functions that provides Helm values, they no longer need to be separated along OperatorController and Catalogd lines; the functions determine where the Helm parameters are set.

Added unit tests, mostly written by Claude Code

Assisted-by: Claude Code

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 16, 2025
@openshift-ci openshift-ci bot requested review from oceanc80 and perdasilva October 16, 2025 16:26
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 16, 2025
@tmshort tmshort force-pushed the disable-feature-gates branch from 6e2ec00 to 39f65b1 Compare October 16, 2025 17:29
Some feature-gates are mutually exclusive, and we need to ensure that
those feature-gates are not simultaneously enabled. In some cames, we
need to disable upstream flags all the time (e.g. WebhookOperatorCertManager).

This defines a function for each downstream feature-gate that defines how
upstream feature-gate flags and arguments should be generated based whether
that downstream feature-gate is enabled or disabled. Because these are
functions that provides Helm values, they no longer need to be separated
along OperatorController and Catalogd lines; the functions determine
where the Helm parameters are set.

Added unit tests, mostly written by Claude Code

Assisted-by: Claude Code

Signed-off-by: Todd Short <todd.short@me.com>
@tmshort tmshort force-pushed the disable-feature-gates branch from 39f65b1 to 0380780 Compare October 16, 2025 17:51
@tmshort
Copy link
Contributor Author

tmshort commented Oct 16, 2025

/test openshift-e2e-aws
Failed due to a [sig-network-edge] test.

@jianzhangbjz
Copy link
Contributor

/assign @bandrade

@jianzhangbjz
Copy link
Contributor

Hi @bandrade , could you help test it? Thanks!

@tmshort
Copy link
Contributor Author

tmshort commented Oct 17, 2025

/retest

Copy link
Contributor

openshift-ci bot commented Oct 17, 2025

@tmshort: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

Copy link

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
Copy link
Contributor

openshift-ci bot commented Oct 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, tmshort

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

@bandrade
Copy link

/lgtm
/verified by @bandrade
/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Oct 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 17, 2025

@tmshort: This pull request references OPRUN-4207 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

Some feature-gates are mutually exclusive, and we need to ensure that those feature-gates are not simultaneously enabled. In some cames, we need to disable upstream flags all the time (e.g. WebhookOperatorCertManager).

This defines a function for each downstream feature-gate that defines how upstream feature-gate flags and arguments should be generated based whether that downstream feature-gate is enabled or disabled. Because these are functions that provides Helm values, they no longer need to be separated along OperatorController and Catalogd lines; the functions determine where the Helm parameters are set.

Added unit tests, mostly written by Claude Code

Assisted-by: Claude Code

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 17, 2025
@openshift-ci-robot
Copy link

@bandrade: This PR has been marked as verified by @bandrade.

In response to this:

/lgtm
/verified by @bandrade
/label qe-approved

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 9bb4d95 into openshift:main Oct 17, 2025
11 checks passed
@tmshort tmshort deleted the disable-feature-gates branch October 17, 2025 17:26
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants