apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.ec2.internal
      uid: a24e167d-ef9f-4d96-852d-0be8435809f3
    resourceVersion: "53039"
    uid: 34c60270-cd5f-409d-b3c6-a6a1a2a50f33
  spec:
    sourcePod: network-check-source-685456655f-jnmld
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:02:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 1.015931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 1.457485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:25Z"
    - latency: 1.196436ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:20:25Z"
    - latency: 1.405524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:25Z"
    - latency: 884.252µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:25Z"
    - latency: 1.014671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:25Z"
    - latency: 1.68303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:25Z"
    - latency: 1.188195ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:25Z"
    - latency: 1.078529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.ec2.internal
      uid: a24e167d-ef9f-4d96-852d-0be8435809f3
    resourceVersion: "54508"
    uid: d1300fae-eac0-481d-8fe0-5ece6785dd41
  spec:
    sourcePod: network-check-source-685456655f-jnmld
    targetEndpoint: ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:01:25Z"
      message: 'load-balancer-api-external: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.815022ms
      message: 'load-balancer-api-external: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:25:25Z"
    - latency: 8.254461ms
      message: 'load-balancer-api-external: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:25:25Z"
    - latency: 3.679763ms
      message: 'load-balancer-api-external: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:24:25Z"
    - latency: 8.740518ms
      message: 'load-balancer-api-external: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:24:25Z"
    - latency: 4.583431ms
      message: 'load-balancer-api-external: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 9.027027ms
      message: 'load-balancer-api-external: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 4.386593ms
      message: 'load-balancer-api-external: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 8.241207ms
      message: 'load-balancer-api-external: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 5.028008ms
      message: 'load-balancer-api-external: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:25Z"
    - latency: 7.206316ms
      message: 'load-balancer-api-external: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.ec2.internal
      uid: a24e167d-ef9f-4d96-852d-0be8435809f3
    resourceVersion: "54509"
    uid: ca58e957-0c31-4ca5-a341-ad24ce442c7f
  spec:
    sourcePod: network-check-source-685456655f-jnmld
    targetEndpoint: ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:01:25Z"
      message: 'load-balancer-api-internal: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.610526ms
      message: 'load-balancer-api-internal: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:25:25Z"
    - latency: 8.336666ms
      message: 'load-balancer-api-internal: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:25:25Z"
    - latency: 4.104525ms
      message: 'load-balancer-api-internal: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:24:25Z"
    - latency: 8.692692ms
      message: 'load-balancer-api-internal: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:24:25Z"
    - latency: 4.380597ms
      message: 'load-balancer-api-internal: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 9.149589ms
      message: 'load-balancer-api-internal: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 4.418129ms
      message: 'load-balancer-api-internal: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 8.177934ms
      message: 'load-balancer-api-internal: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 5.069629ms
      message: 'load-balancer-api-internal: tcp connection to ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:25Z"
    - latency: 7.187582ms
      message: 'load-balancer-api-internal: resolved host name ada8a316f62b14c7fbaeffcc49e0d764-4bbabec0d6106d3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:21:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-ip-10-0-129-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.ec2.internal
      uid: a24e167d-ef9f-4d96-852d-0be8435809f3
    resourceVersion: "53038"
    uid: a44f292f-6c81-461e-9930-1efe0670a00c
  spec:
    sourcePod: network-check-source-685456655f-jnmld
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:02:25Z"
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.428941ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 2.09177ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 2.479577ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:25Z"
    - latency: 2.463078ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:20:25Z"
    - latency: 2.608572ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:25Z"
    - latency: 2.101854ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:25Z"
    - latency: 2.56162ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:25Z"
    - latency: 2.828684ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:25Z"
    - latency: 2.323931ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:25Z"
    - latency: 2.626843ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-ip-10-0-134-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.ec2.internal
      uid: a24e167d-ef9f-4d96-852d-0be8435809f3
    resourceVersion: "53036"
    uid: 512797ba-a8a3-4363-9595-40e72dc40b90
  spec:
    sourcePod: network-check-source-685456655f-jnmld
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:02:25Z"
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.31µs
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 895.81µs
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 934.115µs
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:25Z"
    - latency: 982.939µs
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:20:25Z"
    - latency: 954.775µs
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:25Z"
    - latency: 1.029973ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:25Z"
    - latency: 981.873µs
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:25Z"
    - latency: 1.036438ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:25Z"
    - latency: 1.231986ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:25Z"
    - latency: 1.130135ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-ip-10-0-136-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.ec2.internal
      uid: a24e167d-ef9f-4d96-852d-0be8435809f3
    resourceVersion: "53037"
    uid: 08c5b5b4-119f-4b98-ad57-1f6100f0d9e3
  spec:
    sourcePod: network-check-source-685456655f-jnmld
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:02:25Z"
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.519943ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 2.069576ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 2.535092ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:25Z"
    - latency: 3.065648ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:20:25Z"
    - latency: 2.656253ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:19:25Z"
    - latency: 2.112652ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:18:25Z"
    - latency: 2.488221ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:25Z"
    - latency: 2.420217ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:25Z"
    - latency: 2.603688ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:25Z"
    - latency: 2.543597ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:55:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.ec2.internal
      uid: a24e167d-ef9f-4d96-852d-0be8435809f3
    resourceVersion: "54507"
    uid: 2d756e62-390f-4ade-84dd-12e7c042b013
  spec:
    sourcePod: network-check-source-685456655f-jnmld
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:01:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.290055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:25:25Z"
    - latency: 1.828754ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:25:25Z"
    - latency: 948.087µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:24:25Z"
    - latency: 1.667857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:24:25Z"
    - latency: 1.581954ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 1.881723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:23:25Z"
    - latency: 1.227944ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 1.776397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:22:25Z"
    - latency: 940.555µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:21:25Z"
    - latency: 1.724356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:21:25Z"
kind: List
metadata:
  resourceVersion: ""