apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T19:14:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-31.ec2.internal
      uid: c27bc7e9-363c-4e08-94f2-bf7699456f69
    resourceVersion: "29240"
    uid: 0d0a6f03-568e-406e-acc8-9dd790fac86d
  spec:
    sourcePod: network-check-source-989f8b8dc-xsn6x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T19:21:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 901.357µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:28:47Z"
    - latency: 769.77µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:27:47Z"
    - latency: 1.026273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:26:47Z"
    - latency: 927.957µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:25:47Z"
    - latency: 1.459205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:24:47Z"
    - latency: 971.89µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:23:47Z"
    - latency: 1.096803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:22:47Z"
    - latency: 1.024134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:21:47Z"
    - latency: 1.162824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:20:47Z"
    - latency: 990.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:19:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T19:14:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-31.ec2.internal
      uid: c27bc7e9-363c-4e08-94f2-bf7699456f69
    resourceVersion: "32249"
    uid: c2a2bbf3-1bdb-4720-8352-ae161bbef795
  spec:
    sourcePod: network-check-source-989f8b8dc-xsn6x
    targetEndpoint: a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T19:20:47Z"
      message: 'load-balancer-api-external: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.357865ms
      message: 'load-balancer-api-external: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:32:47Z"
    - latency: 13.477872ms
      message: 'load-balancer-api-external: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:32:47Z"
    - latency: 5.226279ms
      message: 'load-balancer-api-external: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:31:47Z"
    - latency: 8.933159ms
      message: 'load-balancer-api-external: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:31:47Z"
    - latency: 4.209169ms
      message: 'load-balancer-api-external: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:30:47Z"
    - latency: 9.062616ms
      message: 'load-balancer-api-external: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:30:47Z"
    - latency: 4.937074ms
      message: 'load-balancer-api-external: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:29:47Z"
    - latency: 9.80207ms
      message: 'load-balancer-api-external: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:29:47Z"
    - latency: 4.158901ms
      message: 'load-balancer-api-external: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:28:47Z"
    - latency: 7.959948ms
      message: 'load-balancer-api-external: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:28:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T19:14:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-31.ec2.internal
      uid: c27bc7e9-363c-4e08-94f2-bf7699456f69
    resourceVersion: "32250"
    uid: 9247f7ae-b58c-41f7-b76a-5c863d680fae
  spec:
    sourcePod: network-check-source-989f8b8dc-xsn6x
    targetEndpoint: a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T19:20:47Z"
      message: 'load-balancer-api-internal: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.33279ms
      message: 'load-balancer-api-internal: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:32:47Z"
    - latency: 13.554743ms
      message: 'load-balancer-api-internal: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:32:47Z"
    - latency: 5.212003ms
      message: 'load-balancer-api-internal: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:31:47Z"
    - latency: 8.966354ms
      message: 'load-balancer-api-internal: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:31:47Z"
    - latency: 5.011538ms
      message: 'load-balancer-api-internal: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:30:47Z"
    - latency: 9.098923ms
      message: 'load-balancer-api-internal: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:30:47Z"
    - latency: 5.044235ms
      message: 'load-balancer-api-internal: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:29:47Z"
    - latency: 9.846256ms
      message: 'load-balancer-api-internal: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:29:47Z"
    - latency: 5.308088ms
      message: 'load-balancer-api-internal: tcp connection to a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:28:47Z"
    - latency: 7.978945ms
      message: 'load-balancer-api-internal: resolved host name a23f131434bd84c958e3fdf572638e3b-238ab7a0256692d3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:28:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T19:14:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-31-to-network-check-target-ip-10-0-130-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-31.ec2.internal
      uid: c27bc7e9-363c-4e08-94f2-bf7699456f69
    resourceVersion: "29239"
    uid: 00589616-ff89-4014-9fe5-0ab0b39117cd
  spec:
    sourcePod: network-check-source-989f8b8dc-xsn6x
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T19:21:47Z"
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.208918ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:28:47Z"
    - latency: 1.982943ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:27:47Z"
    - latency: 2.220383ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:26:47Z"
    - latency: 2.330901ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:25:47Z"
    - latency: 2.453228ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:24:47Z"
    - latency: 2.274452ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:23:47Z"
    - latency: 2.326116ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:22:47Z"
    - latency: 2.39344ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:21:47Z"
    - latency: 2.103278ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:20:47Z"
    - latency: 2.212401ms
      message: 'network-check-target-ip-10-0-130-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:19:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T19:14:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-31-to-network-check-target-ip-10-0-131-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-31.ec2.internal
      uid: c27bc7e9-363c-4e08-94f2-bf7699456f69
    resourceVersion: "29237"
    uid: c6aa968a-3cce-4c06-bca7-4dcddd946ff8
  spec:
    sourcePod: network-check-source-989f8b8dc-xsn6x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T19:21:47Z"
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.685µs
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:28:47Z"
    - latency: 844.312µs
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:27:47Z"
    - latency: 980.188µs
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:26:47Z"
    - latency: 1.018444ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:25:47Z"
    - latency: 1.277204ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:24:47Z"
    - latency: 1.031384ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:23:47Z"
    - latency: 1.349485ms
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:22:47Z"
    - latency: 941.016µs
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:21:47Z"
    - latency: 844.307µs
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:20:47Z"
    - latency: 862.455µs
      message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:19:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T19:14:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-31-to-network-check-target-ip-10-0-132-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-31.ec2.internal
      uid: c27bc7e9-363c-4e08-94f2-bf7699456f69
    resourceVersion: "29238"
    uid: 06e083dd-d81d-496f-9cad-81f7429e089a
  spec:
    sourcePod: network-check-source-989f8b8dc-xsn6x
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T19:21:47Z"
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.767604ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:28:47Z"
    - latency: 1.596803ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:27:47Z"
    - latency: 1.701914ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:26:47Z"
    - latency: 1.83961ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:25:47Z"
    - latency: 1.721388ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:24:47Z"
    - latency: 1.71377ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:23:47Z"
    - latency: 1.71855ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:22:47Z"
    - latency: 1.739164ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:21:47Z"
    - latency: 1.649482ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:20:47Z"
    - latency: 1.720141ms
      message: 'network-check-target-ip-10-0-132-110: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:19:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T19:14:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-31.ec2.internal
      uid: c27bc7e9-363c-4e08-94f2-bf7699456f69
    resourceVersion: "32248"
    uid: be5a8c9d-693d-4a66-b310-625027ebdf8a
  spec:
    sourcePod: network-check-source-989f8b8dc-xsn6x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T19:20:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.455µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:32:47Z"
    - latency: 1.772192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:32:47Z"
    - latency: 992.416µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:31:47Z"
    - latency: 1.65842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:31:47Z"
    - latency: 812.4µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:30:47Z"
    - latency: 2.077112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:30:47Z"
    - latency: 877.07µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:29:47Z"
    - latency: 1.749271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:29:47Z"
    - latency: 926.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T19:28:47Z"
    - latency: 2.364223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T19:28:47Z"
kind: List
metadata:
  resourceVersion: ""