-
Notifications
You must be signed in to change notification settings - Fork 129
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
deck file kong2kic default use Ingress API, not Gateway API #1427
Comments
same as here! It broke our pipelines :( please fix this, we reverted for 1.40.x version. |
battlebyte
added a commit
that referenced
this issue
Nov 6, 2024
Separate integration tests in kong2kic_integration_test.go and must be explicitly invoked with -tags=integration. Fix tests to evaluate all yaml objects.
Prashansa-K
added a commit
that referenced
this issue
Dec 13, 2024
* fix: restore Gateway API generation (issue #1427). Separate integration tests in kong2kic_integration_test.go and must be explicitly invoked with -tags=integration. Fix tests to evaluate all yaml objects. * refactor: replace hardcoded strings with constants in KIC components * fix: remove nolint directive for service port assignment in createIngressPaths --------- Co-authored-by: Prashansa Kulshrestha <prashkulshrestha@gmail.com>
This issue is fixed in release 1.42.0 |
battlebyte
added a commit
that referenced
this issue
Dec 17, 2024
* fix: restore Gateway API generation (issue #1427). Separate integration tests in kong2kic_integration_test.go and must be explicitly invoked with -tags=integration. Fix tests to evaluate all yaml objects. * refactor: replace hardcoded strings with constants in KIC components * fix: remove nolint directive for service port assignment in createIngressPaths --------- Co-authored-by: Prashansa Kulshrestha <prashkulshrestha@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
v1.41.0
deck file kong2kic -s kong-config.yaml -o gateway.yaml Converted to Ingress API
The text was updated successfully, but these errors were encountered: