-
Notifications
You must be signed in to change notification settings - Fork 62
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
Add a ingresses-only
flag
#67
Comments
@LiorLieberman: The label(s) In response to this:
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. |
Hi! Can I take up this issue? I'll be glad to help |
Hi @camperjett! Sure, thanks! /assign @camperjett |
Hi! I have made the required changes to |
@camperjett, the first thing you'll want to do is make sure existing unit tests are passing. After that, you can build the binary and use the tool with the new flag you added. I think this can be a good place to start with |
How do I use the tool? I am totally new to CNCF eco-system |
You can use the make build target to build it. |
@camperjett are you still working on it, I would like to give it a try 🙂 |
Since we have multiple providers on board now, I'm not sure this is still something we may want to implement. What do you think, @LiorLieberman? |
What would you like to be added:
Add a
ingresses-only
flag to scope the tool to only convert resources without looking for providers CRDsWhy this is needed:
Provider specific support is in early stage support now with only few providers support the conversion. Users might want to scope the tool invocation to only read and convert their ingresses
/good-first-issue
/help-wanted
The text was updated successfully, but these errors were encountered: