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

Make fuzzing easy #456

Open
DirectXMan12 opened this issue May 30, 2019 · 6 comments
Open

Make fuzzing easy #456

DirectXMan12 opened this issue May 30, 2019 · 6 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@DirectXMan12
Copy link
Contributor

We should make fuzzing tests easy to run for conversion.

See also kubernetes-sigs/kubebuilder#725, which mentions kubernetes/kubernetes#75689

@DirectXMan12
Copy link
Contributor Author

/kind feature
/help-wanted

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label May 30, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 28, 2019
@DirectXMan12
Copy link
Contributor Author

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 3, 2019
@vincepri vincepri added this to the v0.5.x milestone Feb 21, 2020
@vincepri
Copy link
Member

Add some helper utilities (example: https://github.com/kubernetes-sigs/cluster-api/blob/master/util/conversion/conversion.go#L133-L157) to controller-runtime

/priority backlog
/help

@k8s-ci-robot
Copy link
Contributor

@vincepri:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Add some helper utilities (example: https://github.com/kubernetes-sigs/cluster-api/blob/master/util/conversion/conversion.go#L133-L157) to controller-runtime

/priority backlog
/help

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Feb 21, 2020
@DavidKorczynski
Copy link

Hi @DirectXMan12

Is this still relevant? If so, we would like to help.

Recently we (@AdamKorcz in particular) have been working on fuzzing custom Kubernetes controllers (Flux GitOps toolkit in this case), please see the following PRs for examples:

It would be neat to fuzz the core controller-runtime library as well (not just limited to conversion libraries), is this something you would be interested in? If so, we are already working on Kubernetes fuzzing (see here: kubernetes/kubernetes#104772) and would be happy extend to the controller-runtime.

(FYI @caniszczyk)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

5 participants