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

https configurations not populated for route? #2518

Closed
zetaab opened this issue Jan 28, 2024 · 1 comment
Closed

https configurations not populated for route? #2518

zetaab opened this issue Jan 28, 2024 · 1 comment
Labels

Comments

@zetaab
Copy link
Contributor

zetaab commented Jan 28, 2024

Description:
I am trying to install envoygateway with proxyprotocol enabled in both http and https. However, it does not work for https.

Repro steps:

install gateway controller

kubectl create ns envoy-gateway-system-external
kubectl label ns envoy-gateway-system-external pod-security.kubernetes.io/audit=baseline --overwrite
kubectl label ns envoy-gateway-system-external pod-security.kubernetes.io/enforce=baseline --overwrite
helm upgrade eg-external oci://docker.io/envoyproxy/gateway-helm --version v0.0.0-latest -n envoy-gateway-system-external --install -f external/values.yaml

values.yaml https://gist.github.com/zetaab/e08c957f0139f87533c55086f7f9ab4e
deploy.yaml: https://gist.github.com/zetaab/4838972dffb7f0143592f058333980a7
app.yaml https://gist.github.com/zetaab/c8ff93b05f460141abe3300a2da09e1d

% curl https://eg-ext.example.com -I
HTTP/2 404 
date: Sun, 28 Jan 2024 16:45:45 GMT
server: envoy
% curl http://eg-ext.example.com -I
HTTP/1.1 200 OK
content-type: application/json; charset=utf-8
content-length: 1298
etag: W/"512-naqzlUgvLR3xY9+dP7je64t35bw"
date: Sun, 28 Jan 2024 16:45:50 GMT
x-envoy-upstream-service-time: 3
server: envoy

Environment:
Kubernetes 1.29.1

Logs:
https://gist.github.com/zetaab/052de1f3d65d4b5b8074df8988183c18 as we can see it does not populate anything under https listeners? Specs https://gateway-api.sigs.k8s.io/guides/implementers/#httproute says

HTTPRoutes route HTTP traffic that is unencrypted and available for inspection. This includes HTTPS traffic that's terminated at the Gateway (since that is then decrypted), and allows the HTTPRoute to use HTTP properties, like path, method, or headers in its routing directives.

So it should work (as it should include terminated traffic in gateway?). Am I missing something in httproute object?

@zetaab zetaab added the triage label Jan 28, 2024
@zetaab zetaab changed the title htt https configurations not populated for route? Jan 28, 2024
@zetaab
Copy link
Contributor Author

zetaab commented Jan 28, 2024

my bad, was missing

      allowedRoutes:
        namespaces:
          from: All

in https listener

@zetaab zetaab closed this as completed Jan 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant