Skip to content

Conversation

@jatinsu
Copy link

@jatinsu jatinsu commented Dec 2, 2025

This PR is to create an enhancement for the OKD featureset.

For more context: openshift/api#2451

@jatinsu jatinsu marked this pull request as draft December 2, 2025 20:27
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 2, 2025
@openshift-ci openshift-ci bot requested review from ashcrow and hasbro17 December 2, 2025 20:27
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 2, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jeffdyoung for approval. For more information see the Code Review Process.

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

Details 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

@jatinsu jatinsu force-pushed the OKD-featuregates branch 2 times, most recently from 075812e to a0218a1 Compare December 10, 2025 16:53
- Resource consumption impact should be minimal as the feature set itself only controls which features are enabled, not the features themselves
- Individual features enabled by the OKD feature set may have their own resource implications

**MicroShift:**
Copy link
Author

Choose a reason for hiding this comment

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

OKD featureset shouldn't affect microshift right?

Copy link
Contributor

Choose a reason for hiding this comment

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

i don't think so, would be good to check with someone in the Microshift team

@Prashanth684 Prashanth684 marked this pull request as ready for review December 12, 2025 18:34
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 12, 2025
@openshift-ci openshift-ci bot requested review from tjungblu and travier December 12, 2025 18:34
@Prashanth684 Prashanth684 changed the title Add OKD featureset enhancement WIP: Add OKD featureset enhancement Dec 12, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 12, 2025
- Resource consumption impact should be minimal as the feature set itself only controls which features are enabled, not the features themselves
- Individual features enabled by the OKD feature set may have their own resource implications

**MicroShift:**
Copy link
Contributor

Choose a reason for hiding this comment

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

i don't think so, would be good to check with someone in the Microshift team

- Condensed enhancement to make it more concise
- reworded some features and addressed comments
- made points into paragraphs and fixed long lines
- Removed version.IsOKD() and explained the logic
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 2025

@jatinsu: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants