Drop Cluster API fuzzing targets #461
Open
Conversation
This file contains 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
Signed-off-by: killianmuldoon <[email protected]>
|
Instead of just removing, I suggest migrating the fuzzers upstream. I will be happy to do that over the next couple of weeks for you. |
That would be great - the main problem is trying to maintain these fuzzers in parallel - moving them upstream to the CAPI repo would remove that problem |
mounicarajput
approved these changes
Sep 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Drop the Cluster API targets from CNCF fuzzing.
Currently the fuzzers for CAPI aren't building and are unmaintained. This has been the case for some time.
Tracking kubernetes-sigs/cluster-api#9548
oss-fuzz PR: google/oss-fuzz#11186