apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:03:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 4dbe200a-5313-40ab-a5d7-5403e04a6d28
    resourceVersion: "32134"
    uid: 924e4dda-5a27-4655-ab7b-9fa4f967d282
  spec:
    sourcePod: network-check-source-7d88cb55d8-xm2wg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:10:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 797.996µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 1.271939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 1.045596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 1.204723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 1.564943ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:58Z"
    - latency: 1.13661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:58Z"
    - latency: 942.491µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:39:58Z"
    - latency: 857.086µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:38:58Z"
    - latency: 1.079606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:37:58Z"
    - latency: 862.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:36:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:03:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 4dbe200a-5313-40ab-a5d7-5403e04a6d28
    resourceVersion: "32135"
    uid: adce3b2f-091d-4805-9ca6-72e7b76a372e
  spec:
    sourcePod: network-check-source-7d88cb55d8-xm2wg
    targetEndpoint: a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:09:58Z"
      message: 'load-balancer-api-external: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.625438ms
      message: 'load-balancer-api-external: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 8.259646ms
      message: 'load-balancer-api-external: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 4.527088ms
      message: 'load-balancer-api-external: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 8.074114ms
      message: 'load-balancer-api-external: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 4.820298ms
      message: 'load-balancer-api-external: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 8.180553ms
      message: 'load-balancer-api-external: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 5.289058ms
      message: 'load-balancer-api-external: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 7.592577ms
      message: 'load-balancer-api-external: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 5.223191ms
      message: 'load-balancer-api-external: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:58Z"
    - latency: 8.630183ms
      message: 'load-balancer-api-external: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:41:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:03:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 4dbe200a-5313-40ab-a5d7-5403e04a6d28
    resourceVersion: "32136"
    uid: 366d1dd3-3ae4-4310-86dd-7c9264df3eed
  spec:
    sourcePod: network-check-source-7d88cb55d8-xm2wg
    targetEndpoint: a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:09:58Z"
      message: 'load-balancer-api-internal: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.628594ms
      message: 'load-balancer-api-internal: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 8.310839ms
      message: 'load-balancer-api-internal: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 4.529759ms
      message: 'load-balancer-api-internal: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 8.131799ms
      message: 'load-balancer-api-internal: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 4.815838ms
      message: 'load-balancer-api-internal: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 8.125131ms
      message: 'load-balancer-api-internal: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 5.301009ms
      message: 'load-balancer-api-internal: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 7.579415ms
      message: 'load-balancer-api-internal: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 6.159539ms
      message: 'load-balancer-api-internal: tcp connection to a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:58Z"
    - latency: 8.59342ms
      message: 'load-balancer-api-internal: resolved host name a13683cccee584422a507e09e70a6dcb-a17f494efeb6bf5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:41:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:03:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-ip-10-0-131-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 4dbe200a-5313-40ab-a5d7-5403e04a6d28
    resourceVersion: "32130"
    uid: 9e7e0d0c-62be-4dc5-98de-b9c1aa460481
  spec:
    sourcePod: network-check-source-7d88cb55d8-xm2wg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:10:58Z"
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 834.392µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 736.189µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 748.359µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 845.421µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 1.55754ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:58Z"
    - latency: 840.6µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:58Z"
    - latency: 1.438575ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:39:58Z"
    - latency: 1.427434ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:38:58Z"
    - latency: 893.883µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:37:58Z"
    - latency: 866.347µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:36:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:03:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-ip-10-0-140-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 4dbe200a-5313-40ab-a5d7-5403e04a6d28
    resourceVersion: "32133"
    uid: 6dc13c13-31c0-416c-b078-2fce3473d38b
  spec:
    sourcePod: network-check-source-7d88cb55d8-xm2wg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:10:58Z"
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.460656ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 2.329788ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 2.021921ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 2.506709ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 2.823119ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:58Z"
    - latency: 2.140834ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:58Z"
    - latency: 2.150867ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:39:58Z"
    - latency: 2.32456ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:38:58Z"
    - latency: 2.104365ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:37:58Z"
    - latency: 2.24556ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:36:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:03:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-ip-10-0-142-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 4dbe200a-5313-40ab-a5d7-5403e04a6d28
    resourceVersion: "32131"
    uid: 16d9001a-d99b-4998-9bac-3f190f6bff14
  spec:
    sourcePod: network-check-source-7d88cb55d8-xm2wg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:10:58Z"
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.206421ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 2.279511ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 2.315739ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 2.253462ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 2.295228ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:58Z"
    - latency: 2.404357ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:40:58Z"
    - latency: 2.329311ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:39:58Z"
    - latency: 2.745388ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:38:58Z"
    - latency: 2.336414ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:37:58Z"
    - latency: 2.333182ms
      message: 'network-check-target-ip-10-0-142-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:36:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T16:03:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 4dbe200a-5313-40ab-a5d7-5403e04a6d28
    resourceVersion: "32132"
    uid: 5d326bcb-ab19-4568-b236-3ec797bfcfaa
  spec:
    sourcePod: network-check-source-7d88cb55d8-xm2wg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T16:09:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.393µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 1.647195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:45:58Z"
    - latency: 933.808µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 1.69689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:44:58Z"
    - latency: 858.72µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 1.789321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:43:58Z"
    - latency: 843.588µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 1.750717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:42:58Z"
    - latency: 1.022202ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T16:41:58Z"
    - latency: 2.193549ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T16:41:58Z"
kind: List
metadata:
  resourceVersion: ""