apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-9.ec2.internal
      uid: 8a2dd4b9-3314-4d6e-b6d4-a88a9d194c1f
    resourceVersion: "54149"
    uid: e7478de4-972c-491a-801e-72bf45608c9b
  spec:
    sourcePod: network-check-source-685456655f-sz8sl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:42:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 1.073003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 1.280974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:34Z"
    - latency: 1.245793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:34Z"
    - latency: 1.001017ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:34Z"
    - latency: 1.113632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:34Z"
    - latency: 934.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:34Z"
    - latency: 1.976531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:34Z"
    - latency: 2.098586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:34Z"
    - latency: 897.161µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-9.ec2.internal
      uid: 8a2dd4b9-3314-4d6e-b6d4-a88a9d194c1f
    resourceVersion: "55849"
    uid: b8195ddf-80db-4314-809d-216535899e17
  spec:
    sourcePod: network-check-source-685456655f-sz8sl
    targetEndpoint: a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:41:34Z"
      message: 'load-balancer-api-external: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.887613ms
      message: 'load-balancer-api-external: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:34Z"
    - latency: 7.404736ms
      message: 'load-balancer-api-external: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:05:34Z"
    - latency: 5.462553ms
      message: 'load-balancer-api-external: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:34Z"
    - latency: 6.490568ms
      message: 'load-balancer-api-external: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:04:34Z"
    - latency: 4.917533ms
      message: 'load-balancer-api-external: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 9.158464ms
      message: 'load-balancer-api-external: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 6.193174ms
      message: 'load-balancer-api-external: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 7.00517ms
      message: 'load-balancer-api-external: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 4.968987ms
      message: 'load-balancer-api-external: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:34Z"
    - latency: 6.887863ms
      message: 'load-balancer-api-external: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-9.ec2.internal
      uid: 8a2dd4b9-3314-4d6e-b6d4-a88a9d194c1f
    resourceVersion: "55850"
    uid: 1c30858f-f532-4e1a-b9d8-75abbdb0a1b5
  spec:
    sourcePod: network-check-source-685456655f-sz8sl
    targetEndpoint: a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:41:34Z"
      message: 'load-balancer-api-internal: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.103544ms
      message: 'load-balancer-api-internal: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:34Z"
    - latency: 7.435977ms
      message: 'load-balancer-api-internal: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:05:34Z"
    - latency: 5.479409ms
      message: 'load-balancer-api-internal: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:34Z"
    - latency: 6.546864ms
      message: 'load-balancer-api-internal: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:04:34Z"
    - latency: 4.817561ms
      message: 'load-balancer-api-internal: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 9.20978ms
      message: 'load-balancer-api-internal: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 6.219425ms
      message: 'load-balancer-api-internal: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 6.980089ms
      message: 'load-balancer-api-internal: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 4.984526ms
      message: 'load-balancer-api-internal: tcp connection to a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:34Z"
    - latency: 6.940972ms
      message: 'load-balancer-api-internal: resolved host name a814c677b10754359bad344b1893a422-f4543a2f0acba038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-9-to-network-check-target-ip-10-0-134-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-9.ec2.internal
      uid: 8a2dd4b9-3314-4d6e-b6d4-a88a9d194c1f
    resourceVersion: "54146"
    uid: 7d3710ed-b3e6-4784-a887-b5bfdf03df9c
  spec:
    sourcePod: network-check-source-685456655f-sz8sl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:42:34Z"
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.059283ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 1.325832ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 1.069127ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:34Z"
    - latency: 1.432278ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:34Z"
    - latency: 1.222721ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:34Z"
    - latency: 1.653571ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:34Z"
    - latency: 870.321µs
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:34Z"
    - latency: 771.521µs
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:34Z"
    - latency: 2.435137ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:34Z"
    - latency: 1.607014ms
      message: 'network-check-target-ip-10-0-134-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-9-to-network-check-target-ip-10-0-136-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-9.ec2.internal
      uid: 8a2dd4b9-3314-4d6e-b6d4-a88a9d194c1f
    resourceVersion: "54148"
    uid: 01f53631-2afb-4205-817d-98acca0dad60
  spec:
    sourcePod: network-check-source-685456655f-sz8sl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:42:34Z"
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.680427ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 2.387158ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 2.488431ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:34Z"
    - latency: 2.529259ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:34Z"
    - latency: 2.911595ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:34Z"
    - latency: 2.310781ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:34Z"
    - latency: 2.160486ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:34Z"
    - latency: 2.770433ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:34Z"
    - latency: 3.880455ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:34Z"
    - latency: 2.445973ms
      message: 'network-check-target-ip-10-0-136-122: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-9-to-network-check-target-ip-10-0-139-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-9.ec2.internal
      uid: 8a2dd4b9-3314-4d6e-b6d4-a88a9d194c1f
    resourceVersion: "54147"
    uid: d67df003-fe73-4114-a04f-8e89495e5942
  spec:
    sourcePod: network-check-source-685456655f-sz8sl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:42:34Z"
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.177468ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 2.467371ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 2.418122ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:34Z"
    - latency: 2.455458ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:00:34Z"
    - latency: 2.621735ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:59:34Z"
    - latency: 1.985972ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:58:34Z"
    - latency: 2.146558ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:57:34Z"
    - latency: 2.398271ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:56:34Z"
    - latency: 3.572009ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:55:34Z"
    - latency: 2.371503ms
      message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:54:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T15:35:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-9.ec2.internal
      uid: 8a2dd4b9-3314-4d6e-b6d4-a88a9d194c1f
    resourceVersion: "55848"
    uid: 3ddc65b1-84bd-4d45-86fc-a9559b489d2b
  spec:
    sourcePod: network-check-source-685456655f-sz8sl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T15:41:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.196µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:05:34Z"
    - latency: 1.938736ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:05:34Z"
    - latency: 1.371167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:04:34Z"
    - latency: 2.09522ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:04:34Z"
    - latency: 983.572µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 1.929983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:03:34Z"
    - latency: 1.442954ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 1.773404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:02:34Z"
    - latency: 1.299505ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:01:34Z"
    - latency: 1.877045ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:01:34Z"
kind: List
metadata:
  resourceVersion: ""