-
Notifications
You must be signed in to change notification settings - Fork 213
Set OKD as default featureset for OKD clusters #1287
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
Open
Prashanth684
wants to merge
2
commits into
openshift:main
Choose a base branch
from
Prashanth684:okd-cvo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| //go:build scos | ||
|
|
||
| package version | ||
|
|
||
| func init() { | ||
| SCOS = true | ||
| } |
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
2 changes: 1 addition & 1 deletion
2
vendor/github.com/openshift/api/config/v1/types_image_policy.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 2518
🏁 Script executed:
# Also check the line count of the file wc -l pkg/start/start.goRepository: openshift/cluster-version-operator
Length of output: 100
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 150
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 113
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 2464
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 1007
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
# Let's check the full integration test file to see what's covered wc -l pkg/start/start_integration_test.goRepository: openshift/cluster-version-operator
Length of output: 117
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 265
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 1019
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 284
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 165
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 3341
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 2519
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 1586
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 7139
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 5458
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 3697
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 1922
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 105
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 1127
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 196
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 96
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 1593
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
🏁 Script executed:
# Check if JSON merge patch is truly idempotent by looking at how k8s handles it web_search Kubernetes JSON merge patch idempotency behaviorRepository: openshift/cluster-version-operator
Length of output: 177
🌐 Web query:
Kubernetes JSON merge patch idempotency behavior MergePatchType💡 Result:
Short answer: JSON Merge Patch (MergePatchType / application/merge-patch+json) is effectively idempotent — applying the same merge patch repeatedly yields the same resulting resource after the first application. This follows the RFC 7386 MergePatch rules (fields are added/replaced; null removes a member), and Kubernetes implements this behavior (JSON-merge replaces lists entirely and uses null to remove fields). Caveats: if your patch is a non-object it replaces the whole document; lists are replaced (not merged); and strategic-merge (the default) has different list semantics. (rfc-editor.org)
Sources:
Citations:
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 132
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 2933
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 370
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 445
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 62
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 2528
🏁 Script executed:
Repository: openshift/cluster-version-operator
Length of output: 60
Add test coverage for Default→OKD migration scenario.
The migration logic is well-implemented and safe:
MergePatchTypepatch (idempotent per RFC 7386)However, the integration tests call
processInitialFeatureGate()but don't explicitly test the migration path itself—they don't set up a cluster with a Default featureset to verify the patch operation and state transition. Consider adding a test case that creates a FeatureGate with Default value and verifies it gets migrated to OKD during startup.