-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Describe the bug
A clear and concise description of what the bug is.
The envoy control plane can now send listeners to envoy, which is good. But I found although the listener is working, it seems the routeconfiguration and clusterloadassignment aren't dispatched to envoy, which result in test failure.
Here is my envoy boostrap configuration yaml:
admin: access_log_path: /root/envoy.log address: socket_address: address: 127.0.0.1 port_value: 19000 dynamic_resources: ads_config: api_type: GRPC transport_api_version: V3 grpc_services: - envoy_grpc: cluster_name: envoyingresscontroller set_node_on_first_message_only: true cds_config: resource_api_version: V3 ads: { } lds_config: resource_api_version: V3 ads: { } node: cluster: test-cluster id: test-id static_resources: clusters: - connect_timeout: 1s load_assignment: cluster_name: envoyingresscontroller endpoints: - lb_endpoints: - endpoint: address: socket_address: address: 127.0.0.1 port_value: 18000 http2_protocol_options: {} name: envoyingresscontroller layered_runtime: layers: - name: runtime-0 rtds_layer: rtds_config: resource_api_version: V3 api_config_source: transport_api_version: V3 api_type: GRPC grpc_services: envoy_grpc: cluster_name: envoyingresscontroller name: runtime-0
envoy logs:
[2021-05-28 10:18:11.264][19694][debug][http] [external/envoy/source/common/http/async_client_impl.cc:100] async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '12'
'grpc-message', 'unknown service envoy.service.runtime.v3.RuntimeDiscoveryService'
I can connect to the ingress pods by using curl -v http://bar.foo.com. But I cannot connect to it by using curl -v http://bar.foo.com:9376, 9376 is the ingress port. It shows the following error:
- About to connect() to bar.foo.com port 9376 (#0)
- Trying 127.0.0.1...
- Connected to bar.foo.com (127.0.0.1) port 9376 (#0)
GET / HTTP/1.1
User-Agent: curl/7.29.0
Host: bar.foo.com:9376
Accept: /
< HTTP/1.1 404 Not Found
< date: Fri, 28 May 2021 02:20:54 GMT
< server: envoy
< content-length: 0
<
- Connection #0 to host bar.foo.com left intact
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.