apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-137.ec2.internal
      uid: e55efed9-5533-435e-b54c-6a1f05204c54
    resourceVersion: "23448"
    uid: 4bd0b371-fcbd-46eb-b917-e43bd4c8b491
  spec:
    sourcePod: network-check-source-6f8b768455-fww7m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:51:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:40Z"
    - latency: 1.056061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:40Z"
    - latency: 943.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:40Z"
    - latency: 899.683µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 794.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 1.042533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 979.825µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 984.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:58:40Z"
    - latency: 945.165µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:57:40Z"
    - latency: 1.153435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-137.ec2.internal
      uid: e55efed9-5533-435e-b54c-6a1f05204c54
    resourceVersion: "22018"
    uid: 22aecbf9-2843-4240-895e-9dc3f60eea9f
  spec:
    sourcePod: network-check-source-6f8b768455-fww7m
    targetEndpoint: af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:40Z"
      message: 'load-balancer-api-external: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.528908ms
      message: 'load-balancer-api-external: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 8.188403ms
      message: 'load-balancer-api-external: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 4.462275ms
      message: 'load-balancer-api-external: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 7.544928ms
      message: 'load-balancer-api-external: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 4.279836ms
      message: 'load-balancer-api-external: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 9.836143ms
      message: 'load-balancer-api-external: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 5.489335ms
      message: 'load-balancer-api-external: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 6.719784ms
      message: 'load-balancer-api-external: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 5.225373ms
      message: 'load-balancer-api-external: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:58:40Z"
    - latency: 7.30002ms
      message: 'load-balancer-api-external: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:58:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-137.ec2.internal
      uid: e55efed9-5533-435e-b54c-6a1f05204c54
    resourceVersion: "22019"
    uid: ae9e5f92-3f5f-473a-8006-0286f9636dc9
  spec:
    sourcePod: network-check-source-6f8b768455-fww7m
    targetEndpoint: af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:40Z"
      message: 'load-balancer-api-internal: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.69735ms
      message: 'load-balancer-api-internal: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 8.292832ms
      message: 'load-balancer-api-internal: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 3.986529ms
      message: 'load-balancer-api-internal: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 7.509195ms
      message: 'load-balancer-api-internal: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 4.369246ms
      message: 'load-balancer-api-internal: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 9.932004ms
      message: 'load-balancer-api-internal: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 5.517922ms
      message: 'load-balancer-api-internal: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 6.690822ms
      message: 'load-balancer-api-internal: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 5.68221ms
      message: 'load-balancer-api-internal: tcp connection to af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:58:40Z"
    - latency: 7.261835ms
      message: 'load-balancer-api-internal: resolved host name af84ad51f0f914caa8959e7081028120-2eb55133e1b74aff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:58:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-137-to-network-check-target-ip-10-0-130-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-137.ec2.internal
      uid: e55efed9-5533-435e-b54c-6a1f05204c54
    resourceVersion: "23447"
    uid: c8731874-03b9-4a5e-a35a-54dd400f0d7c
  spec:
    sourcePod: network-check-source-6f8b768455-fww7m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:51:40Z"
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.098979ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:40Z"
    - latency: 2.609646ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:40Z"
    - latency: 2.360866ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:40Z"
    - latency: 2.264703ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 2.072978ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 2.380792ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 2.375695ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 2.141061ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:58:40Z"
    - latency: 2.381845ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:57:40Z"
    - latency: 2.465148ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-137-to-network-check-target-ip-10-0-131-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-137.ec2.internal
      uid: e55efed9-5533-435e-b54c-6a1f05204c54
    resourceVersion: "23445"
    uid: 5e01e474-9705-41af-9bc4-426d7ab19fda
  spec:
    sourcePod: network-check-source-6f8b768455-fww7m
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:51:40Z"
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.276942ms
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:40Z"
    - latency: 854.989µs
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:40Z"
    - latency: 1.514814ms
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:40Z"
    - latency: 777.662µs
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 719.656µs
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 1.031685ms
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 1.041237ms
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 1.239118ms
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:58:40Z"
    - latency: 1.547715ms
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:57:40Z"
    - latency: 876.24µs
      message: 'network-check-target-ip-10-0-131-137: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-137-to-network-check-target-ip-10-0-143-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-137.ec2.internal
      uid: e55efed9-5533-435e-b54c-6a1f05204c54
    resourceVersion: "23446"
    uid: a3d89cf4-2b83-45b2-a919-d8c828e9ab42
  spec:
    sourcePod: network-check-source-6f8b768455-fww7m
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:51:40Z"
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.09668ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:40Z"
    - latency: 2.234942ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:40Z"
    - latency: 2.40815ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:40Z"
    - latency: 2.348505ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 2.441659ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 2.441636ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 2.46773ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 1.819227ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:58:40Z"
    - latency: 2.380436ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:57:40Z"
    - latency: 2.505534ms
      message: 'network-check-target-ip-10-0-143-155: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:56:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:44:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-137.ec2.internal
      uid: e55efed9-5533-435e-b54c-6a1f05204c54
    resourceVersion: "22017"
    uid: 0b8b7b60-e83a-4666-9521-38d6728efb7c
  spec:
    sourcePod: network-check-source-6f8b768455-fww7m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:50:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.529µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 1.702799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:02:40Z"
    - latency: 1.112018ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 1.682221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:01:40Z"
    - latency: 1.192637ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 1.871629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:00:40Z"
    - latency: 1.052931ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 1.864271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:59:40Z"
    - latency: 997.822µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:58:40Z"
    - latency: 1.610226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:58:40Z"
kind: List
metadata:
  resourceVersion: ""