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

why this config is no healthy upstreams #22158

Closed
13567436138 opened this issue Jul 13, 2022 · 7 comments
Closed

why this config is no healthy upstreams #22158

13567436138 opened this issue Jul 13, 2022 · 7 comments
Labels
area/dns question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@13567436138
Copy link

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.

Title: One line description

Description:

Describe the issue.

apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: cluster
  namespace: istio-system
spec:
  workloadSelector:
    labels:
      istio: ingressgateway
  configPatches:
  - applyTo: NETWORK_FILTER
    match:
      listener:
        #name: 0.0.0.0_8080  
        portNumber: 8080
        filterChain:
          filter:
            name: "envoy.filters.network.http_connection_manager"
    patch:
      operation: MERGE
      value:
        name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": "type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager"
          codec_type: AUTO
          stat_prefix: ingress_http
          route_config:
            name: http.8080
            virtual_hosts:
            - name: “*.8080”
              domains:
              - "*"
              routes:
              - match:
                  caseSensitive: true
                  headers:
                  - name: :method
                    safeRegexMatch:
                      googleRe2: {}
                      regex: G.*T
                  prefix: /
                route:
                  cluster: productpage_cluster
  - applyTo: CLUSTER
    patch:
      operation: ADD
      value:
          name: productpage_cluster
          type: STRICT_DNS
          connect_timeout: 10s
          lb_policy: ROUND_ROBIN
          dns_refresh_rate: 5000ms
          dns_failure_refresh_rate:
            base_interval: 5000ms
            max_interval: 50000ms
          respect_dns_ttl: true
          dns_lookup_family: AUTO
          #dns_resolvers:已废弃
          use_tcp_for_dns_lookups: true
          dns_resolution_config:
            resolvers:
            - socket_address:
                address: 10.68.0.2
                port_value: 53
            dns_resolver_options:
              use_tcp_for_dns_lookups: true
              no_default_search_domain: false
          load_assignment:
            cluster_name: productpage_cluster
            endpoints:
            - lb_endpoints:
              - endpoint:
                  address:
                     socket_address:
                      address: productpage.istio.svc.cluster.local
                      port_value: 9080

[optional Relevant Links:]

Any extra documentation required to understand the issue.

@13567436138 13567436138 added the triage Issue requires triage label Jul 13, 2022
@wbpcode wbpcode added question Questions that are neither investigations, bugs, nor enhancements area/dns and removed triage Issue requires triage labels Jul 13, 2022
@wbpcode
Copy link
Member

wbpcode commented Jul 13, 2022

You can try run a ping command to ensure the dns resolver is working as your expect.

@wbpcode
Copy link
Member

wbpcode commented Jul 13, 2022

cc @yanavlasov

@13567436138
Copy link
Author

[root@node01 ~]# telnet  10.68.0.2 53
Trying 10.68.0.2...
Connected to 10.68.0.2.
Escape character is '^]'.
sdf
sfd
sdfConnection closed by foreign host.
[root@node01 ~]# sdf
bash: sdf: command not found...
[root@node01 ~]# ping  10.68.0.2
PING 10.68.0.2 (10.68.0.2) 56(84) bytes of data.
64 bytes from 10.68.0.2: icmp_seq=1 ttl=64 time=0.041 ms
64 bytes from 10.68.0.2: icmp_seq=2 ttl=64 time=0.024 ms
64 bytes from 10.68.0.2: icmp_seq=3 ttl=64 time=0.023 ms
^C
--- 10.68.0.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2075ms
rtt min/avg/max/mdev = 0.023/0.029/0.041/0.009 ms

@13567436138
Copy link
Author

[root@node01 ~]# kubectl exec -n istio -it busybox-88847f6-l9t8r /bin/sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
/ # ping 10.68.0.2
PING 10.68.0.2 (10.68.0.2): 56 data bytes
64 bytes from 10.68.0.2: seq=0 ttl=64 time=0.066 ms
64 bytes from 10.68.0.2: seq=1 ttl=64 time=0.059 ms
64 bytes from 10.68.0.2: seq=2 ttl=64 time=0.060 ms
64 bytes from 10.68.0.2: seq=3 ttl=64 time=0.058 ms
64 bytes from 10.68.0.2: seq=4 ttl=64 time=0.057 ms
64 bytes from 10.68.0.2: seq=5 ttl=64 time=0.060 ms
64 bytes from 10.68.0.2: seq=6 ttl=64 time=0.058 ms
^X64 bytes from 10.68.0.2: seq=7 ttl=64 time=0.059 ms
^C
--- 10.68.0.2 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 0.057/0.059/0.066 ms
/ # telnet 10.68.0.2 53
Connected to 10.68.0.2
sfds
Connection closed by foreign host
/ # 

@13567436138
Copy link
Author

/ # nslookup productpage.istio.svc.cluster.local 10.68.0.2
Server: 10.68.0.2
Address: 10.68.0.2:53

*** Can't find productpage.istio.svc.cluster.local: No answer

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Aug 13, 2022
@github-actions
Copy link

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dns question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

2 participants