-
Notifications
You must be signed in to change notification settings - Fork 361
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
Envoy's port is not listening in HostNetwork #2813
Comments
cc @Xunzhuo |
You should set
When you are using Refer to: #2374 (comment) |
Since we have supported deployment/svc mergepatch, I think we need to remove hostnetwork support on Envoyproxy API or have a more complete implementation for it. Any thoughts on it @arkodg ? |
Yes let's remove it |
Let me handle it before GA. |
Thanks, change to mergepatch solves this problem: apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
name: eg2
namespace: envoy-gateway-system
spec:
shutdown:
drainTimeout: "1s"
minDrainDuration: "1s"
provider:
type: Kubernetes
kubernetes:
envoyService:
type: ClusterIP
envoyDeployment:
patch:
type: StrategicMerge
value:
spec:
template:
spec:
hostNetwork: true
dnsPolicy: ClusterFirstWithHostNet |
Description:
Envoy's port is not listening if gw pod is set to use HostNetwork, and also there are some error log in envoy pod.
Repro steps:
Use
EnvoyProxy
CR to declare gw pod using HostNetwork, like this:And the gw pod yaml:
The envoy should listen 8899 as it is declared in Gateway CR (envoy listens the same port if Gateway's port > 1024), but envoy did not.
Environment:
envoygateway version: v1.0.0-rc.1
Tested both on single node k3s and the cloud hosted Tencent Kubenretes Engine, got the same result.
Logs:
Logs in envoy container:
The text was updated successfully, but these errors were encountered: