Skip to content
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

Drop Cluster API fuzzing project #11186

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

killianmuldoon
Copy link
Contributor

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

CNCF Fuzzing PR here: cncf/cncf-fuzzing#461

Signed-off-by: killianmuldoon <[email protected]>
Copy link

github-actions bot commented Nov 6, 2023

killianmuldoon (verified) is either the primary contact or is in the CCs list of projects/kubernetes-cluster-api.

@DavidKorczynski
Copy link
Collaborator

Since we're planning to move things upstream in the near future instead cncf/cncf-fuzzing#461 (comment) should we close this?

@killianmuldoon
Copy link
Contributor Author

I think we need to hammer out what "moving upstream" means as it might not be acceptable upstream if it's complex. I would expect moving upstream would make the project unnecessary, but I may be wrong about that.

Can we discuss it on the CAPI issue? kubernetes-sigs/cluster-api#9548

@DavidKorczynski
Copy link
Collaborator

Can we discuss it on the CAPI issue?

Yes, let's wait for @AdamKorcz to reply on that issue

@jonathanmetzman
Copy link
Contributor

Since we're planning on revamping this integration, can you just delete the Dockerfile and build.sh, so that accepting the changed version will be smoother?

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

Successfully merging this pull request may close these issues.

3 participants