feat(conversion): enable best-effort output and silence usage on errors

[Cna59]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR improves the error handling behavior of the ingress2gateway print command to support best-effort conversion:

1. Removes usage display on errors: When conversion errors occur, the usage information is no longer displayed, providing cleaner error output.
2. Enables best-effort conversion: The tool now continues processing and outputs valid converted resources even when some resources contain errors, respecting the --output format flag.

Previously, when encountering errors (e.g., unsupported ImplementationSpecific pathType), the command would:

• Display the full usage help, cluttering the error output
• Not output any successfully converted resources in the requested format

After this change, the command:

• Shows only the error messages without usage information
• Continues conversion and outputs all valid resources in the requested format (YAML/JSON)
• Displays errors at the end for visibility

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?: Yes

The `ingress2gateway print` command now supports best-effort conversion, continuing to output valid resources even when errors are encountered. Error output no longer includes usage information for cleaner display.

---

Testing

To test this PR, use the following command with a file containing both valid and invalid resources:

./ingress2gateway print --input-file best-effort-input.yaml --providers ingress-nginx --output yaml

Test Input (best-effort-input.yaml)

apiVersion: v1
kind: Service
metadata:
  name: valid-service
  namespace: test
spec:
  ports:
  - port: 80
    targetPort: 8080
    name: http
---
apiVersion: v1
kind: Service
metadata:
  name: invalid-service
  namespace: test
spec:
  ports:
  - port: 80
    targetPort: invalid-port
    name: http
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: valid-ingress
  namespace: test
spec:
  ingressClassName: test-class
  rules:
  - host: valid.example.com
    http:
      paths:
      - path: /valid
        pathType: Prefix
        backend:
          service:
            name: valid-service
            port:
              number: 80
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: invalid-backend-ingress
  namespace: test
spec:
  ingressClassName: test-class
  rules:
  - host: invalid.example.com
    http:
      paths:
      - path: /invalid
        pathType: Prefix
        backend:
          service:
            name: invalid-service
            port:
              name: non-existent-port

Expected Output

The command should output valid converted Gateway and HTTPRoute resources in YAML format, followed by error messages:

apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
  annotations:
    gateway.networking.k8s.io/generator: ingress2gateway-v0.5.0-rc1-2-g1877e50-dirty
  name: nginx
  namespace: default
spec:
  gatewayClassName: nginx
  listeners:
  - hostname: nginx.example.com
    name: nginx-example-com-http
    port: 80
    protocol: HTTP
status: {}
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
  annotations:
    gateway.networking.k8s.io/generator: ingress2gateway-v0.5.0-rc1-2-g1877e50-dirty
  name: test-nginx-nginx-example-com
  namespace: default
spec:
  hostnames:
  - nginx.example.com
  parentRefs:
  - name: nginx
status:
  parents: []
Error:

# Encountered 1 errors # spec.rules[0].http.paths[0].pathType: Invalid value: "ImplementationSpecific": implementationSpecific path type is not supported in generic translation, and your provider does not provide custom support to translate it

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Cna59
Once this PR has been reviewed and has the lgtm label, please assign robscott for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Cna59 / name: Maxime Steux (7d35cb9)

[k8s-ci-robot]

Welcome @Cna59!

It looks like this is your first PR to kubernetes-sigs/ingress2gateway 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/ingress2gateway has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Cna59. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[Cna59]

This enables best-effort conversion and allows users to see what could be converted

[Cna59]

This enables best-effort conversion and allows users to see what could be converted

Etc..

[Cna59]

If you do not want the "best-effort" output i can recreate a pull request with only the "silence usage on errors"

[z15alall]

Tested and it's work's usefull to be able to have an output even if there is "error" !

[Stevenjin8]

I'm very supportive of this.

[Stevenjin8]

/ok-to-test

[Stevenjin8]

@Cna59 we're in the middle of a refactor, but now that I'm a maintainer, I'll leave some more detailed thoughts

Right now, we have these errors and we have some notifications. Its not clear when we should use one over another. I'm inclined to say that conversion errors should always be treated as notifications (and thus allow conversion). Would love to hear your thoughts.

[k8s-ci-robot]

PR needs rebase.

Details

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-sigs/prow repository.