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.

Sign up for GitHub

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

Jump to bottom

deck file kong2kic default use Ingress API, not Gateway API #1427

Open
yeVoker opened this issue Oct 24, 2024 · 1 comment · May be fixed by #1431
Open

deck file kong2kic default use Ingress API, not Gateway API #1427

yeVoker opened this issue Oct 24, 2024 · 1 comment · May be fixed by #1431

Comments

@yeVoker
Copy link

yeVoker commented Oct 24, 2024

v1.41.0
deck file kong2kic -s kong-config.yaml -o gateway.yaml Converted to Ingress API
@dichico
Copy link

dichico commented Oct 28, 2024

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
@battlebyte
fix: restore Gateway API generation (issue #1427).
c3e02c0 
Separate integration tests in kong2kic_integration_test.go and must be explicitly invoked with -tags=integration.
Fix tests to evaluate all yaml objects.
@battlebyte battlebyte linked a pull request Nov 12, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: restore Gateway API generation (issue #1427). Kong/deck
2 participants
@dichico @yeVoker