apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: c5213e45-603c-4d60-9fd2-a6debac2aaa3
    resourceVersion: "68552"
    uid: c6f2ed23-b392-4f99-9bb9-3d15f8c81bf2
  spec:
    sourcePod: network-check-source-6f8b768455-phssv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:50:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087852ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 1.08164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 1.040617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 983.072µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:15:13Z"
    - latency: 1.20424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:14:13Z"
    - latency: 1.109036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:13:13Z"
    - latency: 1.015705ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:12:13Z"
    - latency: 1.243535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:11:13Z"
    - latency: 1.013961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:10:13Z"
    - latency: 1.037204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: c5213e45-603c-4d60-9fd2-a6debac2aaa3
    resourceVersion: "69359"
    uid: 0fc25f46-4504-4c1d-ab0e-6a14a38cde2a
  spec:
    sourcePod: network-check-source-6f8b768455-phssv
    targetEndpoint: a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:49:13Z"
      message: 'load-balancer-api-external: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.682982ms
      message: 'load-balancer-api-external: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:19:13Z"
    - latency: 6.601086ms
      message: 'load-balancer-api-external: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:19:13Z"
    - latency: 5.473306ms
      message: 'load-balancer-api-external: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 6.148847ms
      message: 'load-balancer-api-external: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 3.985193ms
      message: 'load-balancer-api-external: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 7.823722ms
      message: 'load-balancer-api-external: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 4.830072ms
      message: 'load-balancer-api-external: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 6.978943ms
      message: 'load-balancer-api-external: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 6.393139ms
      message: 'load-balancer-api-external: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:15:13Z"
    - latency: 8.246118ms
      message: 'load-balancer-api-external: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:15:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: c5213e45-603c-4d60-9fd2-a6debac2aaa3
    resourceVersion: "69358"
    uid: 21dbf46d-3250-4649-8b74-3abf0c0f0f96
  spec:
    sourcePod: network-check-source-6f8b768455-phssv
    targetEndpoint: a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:49:13Z"
      message: 'load-balancer-api-internal: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.79696ms
      message: 'load-balancer-api-internal: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:19:13Z"
    - latency: 6.614101ms
      message: 'load-balancer-api-internal: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:19:13Z"
    - latency: 5.143134ms
      message: 'load-balancer-api-internal: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 6.17446ms
      message: 'load-balancer-api-internal: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 4.032831ms
      message: 'load-balancer-api-internal: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 7.795123ms
      message: 'load-balancer-api-internal: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 4.317407ms
      message: 'load-balancer-api-internal: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 6.895378ms
      message: 'load-balancer-api-internal: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 4.648563ms
      message: 'load-balancer-api-internal: tcp connection to a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:15:13Z"
    - latency: 8.215305ms
      message: 'load-balancer-api-internal: resolved host name a2da3f7a53a1746818e9ff6608ecbd7f-f631ba04d9f1e638.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:15:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-ip-10-0-139-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: c5213e45-603c-4d60-9fd2-a6debac2aaa3
    resourceVersion: "68550"
    uid: 1e123348-79ec-4568-9b92-55e0b076e138
  spec:
    sourcePod: network-check-source-6f8b768455-phssv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:50:13Z"
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.02252ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 2.07682ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 2.274211ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 2.338375ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:15:13Z"
    - latency: 2.487625ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:14:13Z"
    - latency: 2.417156ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:13:13Z"
    - latency: 2.079327ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:12:13Z"
    - latency: 2.092775ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:11:13Z"
    - latency: 2.103947ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:10:13Z"
    - latency: 1.830391ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-ip-10-0-140-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: c5213e45-603c-4d60-9fd2-a6debac2aaa3
    resourceVersion: "68551"
    uid: 3c946d4b-a163-42f2-a16f-d1a8614eae36
  spec:
    sourcePod: network-check-source-6f8b768455-phssv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:50:13Z"
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.228897ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 2.332426ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 2.328351ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 2.45434ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:15:13Z"
    - latency: 2.432016ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:14:13Z"
    - latency: 2.40518ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:13:13Z"
    - latency: 2.38178ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:12:13Z"
    - latency: 2.701371ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:11:13Z"
    - latency: 2.510817ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:10:13Z"
    - latency: 2.30505ms
      message: 'network-check-target-ip-10-0-140-16: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-ip-10-0-143-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: c5213e45-603c-4d60-9fd2-a6debac2aaa3
    resourceVersion: "68549"
    uid: 4e96ed07-3589-4830-becd-ad3a3844db7d
  spec:
    sourcePod: network-check-source-6f8b768455-phssv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:50:13Z"
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.569µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 881.685µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 982.885µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 993.828µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:15:13Z"
    - latency: 1.36287ms
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:14:13Z"
    - latency: 962.717µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:13:13Z"
    - latency: 875.739µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:12:13Z"
    - latency: 916.725µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:11:13Z"
    - latency: 806.128µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:10:13Z"
    - latency: 916.731µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:09:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T11:43:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: c5213e45-603c-4d60-9fd2-a6debac2aaa3
    resourceVersion: "69357"
    uid: fe6ae3d4-c480-487d-b972-a8f0e786d057
  spec:
    sourcePod: network-check-source-6f8b768455-phssv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T11:49:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120437ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:19:13Z"
    - latency: 1.902118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:19:13Z"
    - latency: 1.782627ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 1.666874ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:18:13Z"
    - latency: 1.007772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 1.833452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:17:13Z"
    - latency: 874.238µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 2.186441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:16:13Z"
    - latency: 1.197041ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T12:15:13Z"
    - latency: 1.711132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T12:15:13Z"
kind: List
metadata:
  resourceVersion: ""