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

AKS Istio ingress controller and using k8s gateway api #3707

Closed
veldpworld opened this issue Mar 25, 2025 · 1 comment
Closed

AKS Istio ingress controller and using k8s gateway api #3707

veldpworld opened this issue Mar 25, 2025 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@veldpworld
Copy link

We deployed aks istio 1-23 version ingress controller and using gateway api 1.2

istio version : aks - 1.23
gateway api version: 1.2
error: upstream connect error or disconnect/reset before headers. reset reason: protocol error
reason: when try to download the file it gives the above error.

> POST /ledger/api/v1/documents/download-documents?documentId=a736d26d-6fa1-45e9-a628-310a44a80a7e HTTP/1.1
> Host: dev-finance-erp.cargoes.com
> User-Agent: curl/7.81.0
> accept: */*
> Content-Type: application/json
> Cookie: JSESSIONID=5F69D25B5EE5592A2BDB889797A77DCD; JSESSIONID=796158313F43AFE548B32165926D4C97
> Content-Length: 322
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 502 Bad Gateway
< content-length: 87
< content-type: text/plain
< date: Tue, 25 Mar 2025 07:18:02 GMT
< server: istio-envoy
<
* Connection #0 to host dev-finance-erp.cargoes.com left intact
upstream connect error or disconnect/reset before headers. reset reason: protocol errormyvel@DPW-HO-693:~$

we are not using envoy proxy, we use kubernetes gateway api class to refer the istio controller, using httproute we create ingress and it worked fine for get request, but for downloading any file it gave above error

@veldpworld veldpworld added the kind/bug Categorizes issue or PR as related to a bug. label Mar 25, 2025
@shaneutt shaneutt added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 25, 2025
@shaneutt shaneutt moved this to Triage in Gateway API Pipeline Mar 25, 2025
@shaneutt
Copy link
Member

Hi @veldpworld, sorry you're having trouble with your implementation!

This repository is only for the specification of Gateway API, not implementations. In other words, we host the API itself here but implementations like Istio will take that and make it part of their usable APIs to configure Istio. What you've posted above seems like something implementation-specific to your Istio.

As such, you might want to check in with your cloud provider (you mentioned "AKS Istio", so perhaps they have support specific to that), or if you come to find with certainty the problem is from upstream Istio, consider checking in https://github.com/istio.

@shaneutt shaneutt closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2025
@github-project-automation github-project-automation bot moved this from Triage to Done in Gateway API Pipeline Mar 25, 2025
@shaneutt shaneutt removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Development

No branches or pull requests

2 participants