apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 7998056a-5bd2-445d-8250-5aaab6f19297
    resourceVersion: "33580"
    uid: 441f12fd-0d05-428b-ac14-5c4551a94cf7
  spec:
    sourcePod: network-check-source-685456655f-b465g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 942.048µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 894.994µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 1.07437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 1.097494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 1.144003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:39Z"
    - latency: 933.908µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:39Z"
    - latency: 871.193µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:39Z"
    - latency: 948.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:39Z"
    - latency: 981.76µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:39Z"
    - latency: 949.185µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 7998056a-5bd2-445d-8250-5aaab6f19297
    resourceVersion: "33582"
    uid: 2432a07f-c749-4179-bf46-fd915671a2b7
  spec:
    sourcePod: network-check-source-685456655f-b465g
    targetEndpoint: ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:28:39Z"
      message: 'load-balancer-api-external: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.88181ms
      message: 'load-balancer-api-external: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 9.762679ms
      message: 'load-balancer-api-external: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 4.753078ms
      message: 'load-balancer-api-external: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 8.775419ms
      message: 'load-balancer-api-external: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 4.442277ms
      message: 'load-balancer-api-external: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 8.493835ms
      message: 'load-balancer-api-external: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 4.814699ms
      message: 'load-balancer-api-external: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 8.012714ms
      message: 'load-balancer-api-external: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 3.753755ms
      message: 'load-balancer-api-external: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:39Z"
    - latency: 8.008074ms
      message: 'load-balancer-api-external: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:00:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 7998056a-5bd2-445d-8250-5aaab6f19297
    resourceVersion: "33581"
    uid: a20e4100-bbf5-4e86-839c-1bc44e33dd42
  spec:
    sourcePod: network-check-source-685456655f-b465g
    targetEndpoint: ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:28:39Z"
      message: 'load-balancer-api-internal: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.857287ms
      message: 'load-balancer-api-internal: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 9.816322ms
      message: 'load-balancer-api-internal: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 3.820872ms
      message: 'load-balancer-api-internal: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 8.840402ms
      message: 'load-balancer-api-internal: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 4.408969ms
      message: 'load-balancer-api-internal: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 8.523573ms
      message: 'load-balancer-api-internal: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 4.858453ms
      message: 'load-balancer-api-internal: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 7.975211ms
      message: 'load-balancer-api-internal: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 4.986062ms
      message: 'load-balancer-api-internal: tcp connection to ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:39Z"
    - latency: 7.976344ms
      message: 'load-balancer-api-internal: resolved host name ab5685a430e714f5fbcccfb6e445b65b-669d25b784373e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:00:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-ip-10-0-133-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 7998056a-5bd2-445d-8250-5aaab6f19297
    resourceVersion: "33579"
    uid: 87bb2c74-898b-4be9-b6e0-44d1394bbe08
  spec:
    sourcePod: network-check-source-685456655f-b465g
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:39Z"
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.215187ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 2.302968ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 2.293929ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 2.285608ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 2.209355ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:39Z"
    - latency: 2.240504ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:39Z"
    - latency: 2.228442ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:39Z"
    - latency: 2.259705ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:39Z"
    - latency: 2.39626ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:39Z"
    - latency: 2.24146ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-ip-10-0-140-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 7998056a-5bd2-445d-8250-5aaab6f19297
    resourceVersion: "33576"
    uid: 605c4cd6-4281-46f2-8b9a-293e82e10902
  spec:
    sourcePod: network-check-source-685456655f-b465g
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:39Z"
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.396805ms
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 917.495µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 888.162µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 878.044µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 891.172µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:39Z"
    - latency: 865.616µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:39Z"
    - latency: 1.451636ms
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:39Z"
    - latency: 899.783µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:39Z"
    - latency: 899.47µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:39Z"
    - latency: 875.181µs
      message: 'network-check-target-ip-10-0-140-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-ip-10-0-141-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 7998056a-5bd2-445d-8250-5aaab6f19297
    resourceVersion: "33578"
    uid: 08406f5e-3d06-4744-824e-0f89f2c98074
  spec:
    sourcePod: network-check-source-685456655f-b465g
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:29:39Z"
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.394184ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 2.464201ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 1.926133ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 2.296715ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 2.197028ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:39Z"
    - latency: 2.295124ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:39Z"
    - latency: 2.721709ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:39Z"
    - latency: 2.14757ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:39Z"
    - latency: 2.690607ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:39Z"
    - latency: 2.364006ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-239-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-239.ec2.internal
      uid: 7998056a-5bd2-445d-8250-5aaab6f19297
    resourceVersion: "33577"
    uid: 2d61e22e-aa9e-4800-9e28-ec0b81761516
  spec:
    sourcePod: network-check-source-685456655f-b465g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:28:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.323µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 1.776093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:04:39Z"
    - latency: 780.372µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 1.602494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:03:39Z"
    - latency: 921.666µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 1.69737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:02:39Z"
    - latency: 801.858µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 1.6904ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:01:39Z"
    - latency: 1.338672ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:39Z"
    - latency: 1.901275ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:00:39Z"
kind: List
metadata:
  resourceVersion: ""