apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-79-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-79.ec2.internal
      uid: 6a2c4ae5-b6f9-4a89-bc94-3ea7bc7aa6d4
    resourceVersion: "78529"
    uid: 4416ee9b-3d41-474d-9b7f-0d044c8c41ab
  spec:
    sourcePod: network-check-source-869dcfcdcd-pzjcd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.144857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 1.315467ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 1.000047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 1.115207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:11Z"
    - latency: 1.016367ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:11Z"
    - latency: 900.548µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:11Z"
    - latency: 1.107379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:11Z"
    - latency: 951.349µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:11Z"
    - latency: 936.676µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:11Z"
    - latency: 1.443213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-79-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-79.ec2.internal
      uid: 6a2c4ae5-b6f9-4a89-bc94-3ea7bc7aa6d4
    resourceVersion: "79342"
    uid: d53ae5f3-2248-41c5-8398-04c72a43bd13
  spec:
    sourcePod: network-check-source-869dcfcdcd-pzjcd
    targetEndpoint: a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:11Z"
      message: 'load-balancer-api-external: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.100106ms
      message: 'load-balancer-api-external: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:26:11Z"
    - latency: 8.245059ms
      message: 'load-balancer-api-external: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:26:11Z"
    - latency: 6.41026ms
      message: 'load-balancer-api-external: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 9.690839ms
      message: 'load-balancer-api-external: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 5.827073ms
      message: 'load-balancer-api-external: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 8.938074ms
      message: 'load-balancer-api-external: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 4.294817ms
      message: 'load-balancer-api-external: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 8.246782ms
      message: 'load-balancer-api-external: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 4.913369ms
      message: 'load-balancer-api-external: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:11Z"
    - latency: 8.485821ms
      message: 'load-balancer-api-external: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-79-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-79.ec2.internal
      uid: 6a2c4ae5-b6f9-4a89-bc94-3ea7bc7aa6d4
    resourceVersion: "79341"
    uid: 7610d2bc-9ea7-4c9e-bbf5-b32415e5ca7c
  spec:
    sourcePod: network-check-source-869dcfcdcd-pzjcd
    targetEndpoint: a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:11Z"
      message: 'load-balancer-api-internal: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.142303ms
      message: 'load-balancer-api-internal: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:26:11Z"
    - latency: 8.130773ms
      message: 'load-balancer-api-internal: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:26:11Z"
    - latency: 4.332324ms
      message: 'load-balancer-api-internal: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 9.621957ms
      message: 'load-balancer-api-internal: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 3.887207ms
      message: 'load-balancer-api-internal: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 8.885107ms
      message: 'load-balancer-api-internal: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 4.295844ms
      message: 'load-balancer-api-internal: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 8.141237ms
      message: 'load-balancer-api-internal: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 4.910775ms
      message: 'load-balancer-api-internal: tcp connection to a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:11Z"
    - latency: 8.366385ms
      message: 'load-balancer-api-internal: resolved host name a764e0fb0d810454588d653421b3d422-b21387e8c19fe429.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:22:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-79-to-network-check-target-ip-10-0-129-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-79.ec2.internal
      uid: 6a2c4ae5-b6f9-4a89-bc94-3ea7bc7aa6d4
    resourceVersion: "78527"
    uid: f80e0668-2ea2-47ad-93fe-779c72d9e42a
  spec:
    sourcePod: network-check-source-869dcfcdcd-pzjcd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:11Z"
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.829278ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 2.078083ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 1.805424ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 2.008781ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:11Z"
    - latency: 1.731567ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:11Z"
    - latency: 1.744017ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:11Z"
    - latency: 2.155013ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:11Z"
    - latency: 1.953681ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:11Z"
    - latency: 1.993864ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:11Z"
    - latency: 2.864097ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-79-to-network-check-target-ip-10-0-131-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-79.ec2.internal
      uid: 6a2c4ae5-b6f9-4a89-bc94-3ea7bc7aa6d4
    resourceVersion: "78528"
    uid: af7e024e-2187-46ed-90eb-941eb8e2e08b
  spec:
    sourcePod: network-check-source-869dcfcdcd-pzjcd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:11Z"
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.031051ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 2.076548ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 2.160502ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 2.232693ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:11Z"
    - latency: 2.264567ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:11Z"
    - latency: 2.241555ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:11Z"
    - latency: 2.480995ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:11Z"
    - latency: 2.381243ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:11Z"
    - latency: 2.295278ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:11Z"
    - latency: 2.160754ms
      message: 'network-check-target-ip-10-0-131-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-79-to-network-check-target-ip-10-0-137-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-79.ec2.internal
      uid: 6a2c4ae5-b6f9-4a89-bc94-3ea7bc7aa6d4
    resourceVersion: "78526"
    uid: b5582b0f-6ece-4814-823e-d7a60904e82a
  spec:
    sourcePod: network-check-source-869dcfcdcd-pzjcd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:11Z"
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.911µs
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 1.404633ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 932.181µs
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 910.065µs
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:11Z"
    - latency: 1.276272ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:11Z"
    - latency: 767.651µs
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:11Z"
    - latency: 922.397µs
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:11Z"
    - latency: 1.113729ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:11Z"
    - latency: 925.94µs
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:11Z"
    - latency: 1.581283ms
      message: 'network-check-target-ip-10-0-137-79: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-79-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-79.ec2.internal
      uid: 6a2c4ae5-b6f9-4a89-bc94-3ea7bc7aa6d4
    resourceVersion: "79339"
    uid: 4656b56f-fb56-4c3b-8e03-43d2ea10fc75
  spec:
    sourcePod: network-check-source-869dcfcdcd-pzjcd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.165µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:26:11Z"
    - latency: 1.842877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:26:11Z"
    - latency: 900.305µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 1.79994ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:25:11Z"
    - latency: 924.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 1.85424ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:24:11Z"
    - latency: 964.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 1.949871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:23:11Z"
    - latency: 806.026µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:11Z"
    - latency: 1.720696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:22:11Z"
kind: List
metadata:
  resourceVersion: ""