apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T22:31:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-116-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-116.ec2.internal
      uid: 5e2bc65a-3d29-411c-8122-8c164776478a
    resourceVersion: "68480"
    uid: d3a81a61-f244-410c-a53d-7adaaa4de171
  spec:
    sourcePod: network-check-source-6f8b768455-h6msr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T22:38:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.881µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 852.724µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 1.188519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 1.057835ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:03:35Z"
    - latency: 924.087µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:02:35Z"
    - latency: 1.28219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:01:35Z"
    - latency: 1.288167ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:00:35Z"
    - latency: 1.338488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:59:35Z"
    - latency: 1.007818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:58:35Z"
    - latency: 1.083481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:57:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T22:31:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-116-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-116.ec2.internal
      uid: 5e2bc65a-3d29-411c-8122-8c164776478a
    resourceVersion: "69391"
    uid: ec624287-8b54-4fd4-a1c6-fd0b3c0ac361
  spec:
    sourcePod: network-check-source-6f8b768455-h6msr
    targetEndpoint: a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T22:37:35Z"
      message: 'load-balancer-api-external: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.093462ms
      message: 'load-balancer-api-external: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:07:35Z"
    - latency: 7.649024ms
      message: 'load-balancer-api-external: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:07:35Z"
    - latency: 3.979577ms
      message: 'load-balancer-api-external: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 7.670632ms
      message: 'load-balancer-api-external: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 5.542483ms
      message: 'load-balancer-api-external: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 8.395992ms
      message: 'load-balancer-api-external: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 4.048656ms
      message: 'load-balancer-api-external: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 8.379389ms
      message: 'load-balancer-api-external: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 5.828852ms
      message: 'load-balancer-api-external: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:03:35Z"
    - latency: 7.866329ms
      message: 'load-balancer-api-external: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:03:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T22:31:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-116-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-116.ec2.internal
      uid: 5e2bc65a-3d29-411c-8122-8c164776478a
    resourceVersion: "69390"
    uid: 2d322c29-ea16-4f52-833b-39951370fc98
  spec:
    sourcePod: network-check-source-6f8b768455-h6msr
    targetEndpoint: a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T22:37:35Z"
      message: 'load-balancer-api-internal: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.525744ms
      message: 'load-balancer-api-internal: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:07:35Z"
    - latency: 7.680712ms
      message: 'load-balancer-api-internal: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:07:35Z"
    - latency: 4.190493ms
      message: 'load-balancer-api-internal: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 7.714976ms
      message: 'load-balancer-api-internal: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 5.193959ms
      message: 'load-balancer-api-internal: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 8.384258ms
      message: 'load-balancer-api-internal: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 3.976204ms
      message: 'load-balancer-api-internal: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 8.452177ms
      message: 'load-balancer-api-internal: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 6.344483ms
      message: 'load-balancer-api-internal: tcp connection to a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:03:35Z"
    - latency: 7.830541ms
      message: 'load-balancer-api-internal: resolved host name a99941f6fbc0b40689c9910ec4cf2ab8-c0cb2c588ef0a614.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:03:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T22:31:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-116-to-network-check-target-ip-10-0-128-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-116.ec2.internal
      uid: 5e2bc65a-3d29-411c-8122-8c164776478a
    resourceVersion: "68478"
    uid: f0fe5e6e-87b6-4c25-bfac-33419f60a6ce
  spec:
    sourcePod: network-check-source-6f8b768455-h6msr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T22:38:35Z"
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.155831ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 2.196078ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 2.433713ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 2.307482ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:03:35Z"
    - latency: 2.336281ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:02:35Z"
    - latency: 2.215014ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:01:35Z"
    - latency: 2.320821ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:00:35Z"
    - latency: 2.578754ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:59:35Z"
    - latency: 2.501254ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:58:35Z"
    - latency: 2.495791ms
      message: 'network-check-target-ip-10-0-128-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:57:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T22:31:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-116-to-network-check-target-ip-10-0-128-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-116.ec2.internal
      uid: 5e2bc65a-3d29-411c-8122-8c164776478a
    resourceVersion: "68479"
    uid: 20ba55a9-a9c3-407a-9e2f-ea84afbd3a70
  spec:
    sourcePod: network-check-source-6f8b768455-h6msr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T22:38:35Z"
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.922698ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 1.949494ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 2.090478ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 2.033715ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:03:35Z"
    - latency: 2.001186ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:02:35Z"
    - latency: 2.136341ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:01:35Z"
    - latency: 2.34402ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:00:35Z"
    - latency: 2.398119ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:59:35Z"
    - latency: 2.457864ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:58:35Z"
    - latency: 2.539146ms
      message: 'network-check-target-ip-10-0-128-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:57:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T22:31:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-116-to-network-check-target-ip-10-0-138-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-116.ec2.internal
      uid: 5e2bc65a-3d29-411c-8122-8c164776478a
    resourceVersion: "68477"
    uid: 212752c1-779a-4427-9bec-b7480002e3f1
  spec:
    sourcePod: network-check-source-6f8b768455-h6msr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T22:38:35Z"
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.709µs
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 952.404µs
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 1.138671ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 1.072314ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:03:35Z"
    - latency: 947.179µs
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:02:35Z"
    - latency: 936.655µs
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:01:35Z"
    - latency: 1.263641ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:00:35Z"
    - latency: 1.22548ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:59:35Z"
    - latency: 1.817521ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:58:35Z"
    - latency: 867.193µs
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T22:57:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T22:31:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-116-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-116.ec2.internal
      uid: 5e2bc65a-3d29-411c-8122-8c164776478a
    resourceVersion: "69389"
    uid: 2ab9a916-0a5c-415e-a94c-d37ae901c8ac
  spec:
    sourcePod: network-check-source-6f8b768455-h6msr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T22:37:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.17888ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:07:35Z"
    - latency: 1.70673ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:07:35Z"
    - latency: 931.616µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 2.253477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:06:35Z"
    - latency: 1.002865ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 1.987489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:05:35Z"
    - latency: 856.929µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 1.853026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:04:35Z"
    - latency: 868.292µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T23:03:35Z"
    - latency: 1.872903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T23:03:35Z"
kind: List
metadata:
  resourceVersion: ""