apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T18:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-45.ec2.internal
      uid: 97f4ed47-4f29-43cd-9ab8-445ac9a41b6b
    resourceVersion: "64380"
    uid: 9f75dec2-81aa-4251-8aeb-bd7c35134a5a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-56qcg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T18:27:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.128233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 1.142155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 1.075303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 840.844µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 1.296998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:58:57Z"
    - latency: 837.605µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:57:57Z"
    - latency: 1.186666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:56:57Z"
    - latency: 1.191623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:55:57Z"
    - latency: 1.094916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:54:57Z"
    - latency: 1.280893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T18:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-45.ec2.internal
      uid: 97f4ed47-4f29-43cd-9ab8-445ac9a41b6b
    resourceVersion: "64382"
    uid: c83b499f-c94d-4c1c-b5a9-43238c9800b1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-56qcg
    targetEndpoint: aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T18:26:57Z"
      message: 'load-balancer-api-external: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.609599ms
      message: 'load-balancer-api-external: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 9.205606ms
      message: 'load-balancer-api-external: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 6.099033ms
      message: 'load-balancer-api-external: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 8.377101ms
      message: 'load-balancer-api-external: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 4.343003ms
      message: 'load-balancer-api-external: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 8.376336ms
      message: 'load-balancer-api-external: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 3.839062ms
      message: 'load-balancer-api-external: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 8.388308ms
      message: 'load-balancer-api-external: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 3.686172ms
      message: 'load-balancer-api-external: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:58:57Z"
    - latency: 10.148804ms
      message: 'load-balancer-api-external: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T18:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T18:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-45.ec2.internal
      uid: 97f4ed47-4f29-43cd-9ab8-445ac9a41b6b
    resourceVersion: "64381"
    uid: 1209c343-7770-494b-b39b-0092be1ebadf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-56qcg
    targetEndpoint: aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T18:26:57Z"
      message: 'load-balancer-api-internal: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.618571ms
      message: 'load-balancer-api-internal: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 9.252087ms
      message: 'load-balancer-api-internal: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 6.070121ms
      message: 'load-balancer-api-internal: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 8.346874ms
      message: 'load-balancer-api-internal: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 3.922885ms
      message: 'load-balancer-api-internal: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 8.34556ms
      message: 'load-balancer-api-internal: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 5.268463ms
      message: 'load-balancer-api-internal: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 8.42179ms
      message: 'load-balancer-api-internal: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 3.725695ms
      message: 'load-balancer-api-internal: tcp connection to aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:58:57Z"
    - latency: 10.02339ms
      message: 'load-balancer-api-internal: resolved host name aa294135bea974c358e6818d93fe584c-00010d88170086a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T18:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T18:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-45-to-network-check-target-ip-10-0-129-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-45.ec2.internal
      uid: 97f4ed47-4f29-43cd-9ab8-445ac9a41b6b
    resourceVersion: "64377"
    uid: 3e6d9acd-8dd3-4ca0-918b-52716bfdb1c4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-56qcg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T18:27:57Z"
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.284195ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 1.911084ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 2.057334ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 2.014137ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 2.108895ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:58:57Z"
    - latency: 2.109993ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:57:57Z"
    - latency: 2.130682ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:56:57Z"
    - latency: 2.15679ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:55:57Z"
    - latency: 2.000775ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:54:57Z"
    - latency: 2.213878ms
      message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T18:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-45-to-network-check-target-ip-10-0-138-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-45.ec2.internal
      uid: 97f4ed47-4f29-43cd-9ab8-445ac9a41b6b
    resourceVersion: "64376"
    uid: b5c6d9c2-fd7d-402f-b2e0-36e0a667a744
  spec:
    sourcePod: network-check-source-7bc5b6bf85-56qcg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T18:27:57Z"
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 763.261µs
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 1.56219ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 897.622µs
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 1.137702ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 876.181µs
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:58:57Z"
    - latency: 1.008499ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:57:57Z"
    - latency: 1.050799ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:56:57Z"
    - latency: 1.417139ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:55:57Z"
    - latency: 857.408µs
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:54:57Z"
    - latency: 1.545304ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T18:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-45-to-network-check-target-ip-10-0-142-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-45.ec2.internal
      uid: 97f4ed47-4f29-43cd-9ab8-445ac9a41b6b
    resourceVersion: "64378"
    uid: 258cb365-2576-4965-be91-5ee4b227e898
  spec:
    sourcePod: network-check-source-7bc5b6bf85-56qcg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T18:27:57Z"
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.063052ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 2.210981ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 2.237918ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 2.160528ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 2.303712ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:58:57Z"
    - latency: 1.999817ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:57:57Z"
    - latency: 2.142726ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:56:57Z"
    - latency: 2.145749ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:55:57Z"
    - latency: 1.887567ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:54:57Z"
    - latency: 2.024445ms
      message: 'network-check-target-ip-10-0-142-149: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:53:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T18:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-45.ec2.internal
      uid: 97f4ed47-4f29-43cd-9ab8-445ac9a41b6b
    resourceVersion: "64379"
    uid: 592873a9-a6c4-4f09-9f31-cde92674119e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-56qcg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T18:26:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.973µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 1.792823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:02:57Z"
    - latency: 940.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 2.186297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:01:57Z"
    - latency: 1.278545ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 1.631191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T19:00:57Z"
    - latency: 968.466µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 1.681758ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T18:59:57Z"
    - latency: 1.065699ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T18:58:57Z"
    - latency: 1.723337ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T18:58:57Z"
kind: List
metadata:
  resourceVersion: ""