apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T22:51:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-222-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-222.us-east-2.compute.internal uid: c5afa02b-0ba0-4d22-a380-c35dd41942c1 resourceVersion: "126935" uid: eb8279de-392b-4921-9bee-26a4b296e5df spec: sourcePod: network-check-source-6f78d59f99-cbfsw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T22:58:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.296071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:47:52Z" - latency: 2.868072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:46:52Z" - latency: 1.001363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:45:52Z" - latency: 1.427817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:44:52Z" - latency: 986.142µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:43:52Z" - latency: 901.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:42:52Z" - latency: 1.238122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:41:52Z" - latency: 1.071924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:40:52Z" - latency: 1.33079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:39:52Z" - latency: 795.434µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:38:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T22:51:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-222-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-222.us-east-2.compute.internal uid: c5afa02b-0ba0-4d22-a380-c35dd41942c1 resourceVersion: "125540" uid: 75acb22d-197f-4910-8a25-b63b96e0d46f spec: sourcePod: network-check-source-6f78d59f99-cbfsw targetEndpoint: aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T23:21:52Z" message: 'load-balancer-api-external: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 13.600133616s message: 'load-balancer-api-external: failure looking up host aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: dial tcp: lookup aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:02Z" outages: - end: "2026-10-31T23:20:57Z" endLogs: - latency: 4.85952ms message: 'load-balancer-api-external: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:20:57Z" - latency: 13.600133616s message: 'load-balancer-api-external: failure looking up host aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: dial tcp: lookup aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:02Z" message: Connectivity restored after 54.425794149s start: "2026-10-31T23:20:02Z" startLogs: - latency: 13.600133616s message: 'load-balancer-api-external: failure looking up host aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: dial tcp: lookup aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:02Z" successes: - latency: 5.658796ms message: 'load-balancer-api-external: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:45:52Z" - latency: 7.647914ms message: 'load-balancer-api-external: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:45:52Z" - latency: 6.985433ms message: 'load-balancer-api-external: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:44:52Z" - latency: 7.135602ms message: 'load-balancer-api-external: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:44:52Z" - latency: 6.064929ms message: 'load-balancer-api-external: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:43:52Z" - latency: 7.109252ms message: 'load-balancer-api-external: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:43:52Z" - latency: 6.045787ms message: 'load-balancer-api-external: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:42:52Z" - latency: 6.769956ms message: 'load-balancer-api-external: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:42:52Z" - latency: 6.636801ms message: 'load-balancer-api-external: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:41:52Z" - latency: 7.030751ms message: 'load-balancer-api-external: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:41:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T22:51:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-222-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-222.us-east-2.compute.internal uid: c5afa02b-0ba0-4d22-a380-c35dd41942c1 resourceVersion: "125541" uid: 4bcee73c-4f8b-4780-8b4b-58a49e49d6d8 spec: sourcePod: network-check-source-6f78d59f99-cbfsw targetEndpoint: aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T23:21:52Z" message: 'load-balancer-api-internal: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 13.238197075s message: 'load-balancer-api-internal: failure looking up host aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: dial tcp: lookup aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:03Z" outages: - end: "2026-10-31T23:20:57Z" endLogs: - latency: 5.257294ms message: 'load-balancer-api-internal: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:20:57Z" - latency: 13.238197075s message: 'load-balancer-api-internal: failure looking up host aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: dial tcp: lookup aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:03Z" message: Connectivity restored after 54.271960398s start: "2026-10-31T23:20:03Z" startLogs: - latency: 13.238197075s message: 'load-balancer-api-internal: failure looking up host aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: dial tcp: lookup aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:03Z" successes: - latency: 5.739373ms message: 'load-balancer-api-internal: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:45:52Z" - latency: 7.578861ms message: 'load-balancer-api-internal: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:45:52Z" - latency: 7.019652ms message: 'load-balancer-api-internal: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:44:52Z" - latency: 7.056521ms message: 'load-balancer-api-internal: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:44:52Z" - latency: 6.502594ms message: 'load-balancer-api-internal: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:43:52Z" - latency: 7.057423ms message: 'load-balancer-api-internal: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:43:52Z" - latency: 6.154331ms message: 'load-balancer-api-internal: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:42:52Z" - latency: 6.710536ms message: 'load-balancer-api-internal: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:42:52Z" - latency: 6.110179ms message: 'load-balancer-api-internal: tcp connection to aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:41:52Z" - latency: 6.96686ms message: 'load-balancer-api-internal: resolved host name aac506b80ccd7492998029ac9820eb2b-24b6d51f56921910.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T23:41:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T22:51:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-222-to-network-check-target-ip-10-0-131-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-222.us-east-2.compute.internal uid: c5afa02b-0ba0-4d22-a380-c35dd41942c1 resourceVersion: "126934" uid: be62fbe4-7453-4687-9383-cd5e8fa9ef1e spec: sourcePod: network-check-source-6f78d59f99-cbfsw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T22:58:52Z" message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.078806ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:47:52Z" - latency: 5.776173ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:46:52Z" - latency: 2.343927ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:45:52Z" - latency: 2.23596ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:44:52Z" - latency: 2.000546ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:43:52Z" - latency: 1.565806ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:42:52Z" - latency: 1.904582ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:41:52Z" - latency: 2.382587ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:40:52Z" - latency: 2.317905ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:39:52Z" - latency: 1.667679ms message: 'network-check-target-ip-10-0-131-157: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:38:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T23:21:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-222-to-network-check-target-ip-10-0-133-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-222.us-east-2.compute.internal uid: c5afa02b-0ba0-4d22-a380-c35dd41942c1 resourceVersion: "118315" uid: 1c86e2b9-ec2e-4b8c-982d-9ad8f5c1dba7 spec: sourcePod: network-check-source-6f78d59f99-cbfsw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T23:28:24Z" message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.048551ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:42:24Z" - latency: 950.231µs message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:41:24Z" - latency: 1.061708ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:40:24Z" - latency: 1.092573ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:39:24Z" - latency: 1.061948ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:38:24Z" - latency: 879.504µs message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:37:24Z" - latency: 1.116314ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:36:24Z" - latency: 1.436809ms message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:35:24Z" - latency: 934.39µs message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:34:24Z" - latency: 864.218µs message: 'network-check-target-ip-10-0-133-222: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:33:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T22:51:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-222-to-network-check-target-ip-10-0-135-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-222.us-east-2.compute.internal uid: c5afa02b-0ba0-4d22-a380-c35dd41942c1 resourceVersion: "126933" uid: 4a8a47f0-7930-44b6-93a1-4a45a6527097 spec: sourcePod: network-check-source-6f78d59f99-cbfsw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T22:58:52Z" message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.207753ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:47:52Z" - latency: 3.824435ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:46:52Z" - latency: 1.917105ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:45:52Z" - latency: 2.280729ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:44:52Z" - latency: 1.968701ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:43:52Z" - latency: 2.087988ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:42:52Z" - latency: 1.91776ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:41:52Z" - latency: 2.248704ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:40:52Z" - latency: 3.147985ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:39:52Z" - latency: 1.653675ms message: 'network-check-target-ip-10-0-135-163: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:38:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T22:51:51Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-222-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-222.us-east-2.compute.internal uid: c5afa02b-0ba0-4d22-a380-c35dd41942c1 resourceVersion: "125539" uid: df944ac8-4eb6-4f69-86e4-051c44a4e88b spec: sourcePod: network-check-source-6f78d59f99-cbfsw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T23:21:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable failures: - latency: 13.235510269s message: 'network-check-target-service-cluster: failure looking up host network-check-target: dial tcp: lookup network-check-target: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:03Z" outages: - end: "2026-10-31T23:20:57Z" endLogs: - latency: 872.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:20:57Z" - latency: 13.235510269s message: 'network-check-target-service-cluster: failure looking up host network-check-target: dial tcp: lookup network-check-target: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:03Z" message: Connectivity restored after 54.218252239s start: "2026-10-31T23:20:03Z" startLogs: - latency: 13.235510269s message: 'network-check-target-service-cluster: failure looking up host network-check-target: dial tcp: lookup network-check-target: i/o timeout' reason: DNSError success: false time: "2026-10-31T23:20:03Z" successes: - latency: 851.293µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:45:52Z" - latency: 1.958029ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T23:45:52Z" - latency: 953.754µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:44:52Z" - latency: 1.867113ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T23:44:52Z" - latency: 1.125249ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:43:52Z" - latency: 2.003597ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T23:43:52Z" - latency: 880.542µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:42:52Z" - latency: 2.08846ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T23:42:52Z" - latency: 1.418685ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T23:41:52Z" - latency: 1.835843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T23:41:52Z" kind: List metadata: resourceVersion: ""