apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:45:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-175-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-175.ec2.internal
      uid: e9c88479-9715-464a-953c-53c503ef4e24
    resourceVersion: "30103"
    uid: 1638d9d9-2fc3-47bc-9ecb-dc46a97a16b4
  spec:
    sourcePod: network-check-source-56d84b9f44-27db7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:52:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.542µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:30Z"
    - latency: 1.06741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:30Z"
    - latency: 1.420621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 1.083435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 1.10622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 1.001077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 1.088426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:53:30Z"
    - latency: 1.145741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:52:30Z"
    - latency: 1.194991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:51:30Z"
    - latency: 1.278089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:50:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:45:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-175-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-175.ec2.internal
      uid: e9c88479-9715-464a-953c-53c503ef4e24
    resourceVersion: "28546"
    uid: a9ba4335-eb32-4500-8bd2-f02eab5c135e
  spec:
    sourcePod: network-check-source-56d84b9f44-27db7
    targetEndpoint: a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:51:30Z"
      message: 'load-balancer-api-external: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.027607ms
      message: 'load-balancer-api-external: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 7.110447ms
      message: 'load-balancer-api-external: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 6.158575ms
      message: 'load-balancer-api-external: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 7.362924ms
      message: 'load-balancer-api-external: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 5.53641ms
      message: 'load-balancer-api-external: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 7.91514ms
      message: 'load-balancer-api-external: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 5.797718ms
      message: 'load-balancer-api-external: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 14.27428ms
      message: 'load-balancer-api-external: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 4.010614ms
      message: 'load-balancer-api-external: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:53:30Z"
    - latency: 6.892142ms
      message: 'load-balancer-api-external: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:45:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-175-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-175.ec2.internal
      uid: e9c88479-9715-464a-953c-53c503ef4e24
    resourceVersion: "28547"
    uid: 5545829e-89e1-449f-babf-1af5c85c203e
  spec:
    sourcePod: network-check-source-56d84b9f44-27db7
    targetEndpoint: a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:51:30Z"
      message: 'load-balancer-api-internal: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.213049ms
      message: 'load-balancer-api-internal: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 7.068867ms
      message: 'load-balancer-api-internal: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 6.166733ms
      message: 'load-balancer-api-internal: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 7.332292ms
      message: 'load-balancer-api-internal: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 5.556748ms
      message: 'load-balancer-api-internal: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 7.890835ms
      message: 'load-balancer-api-internal: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 5.806324ms
      message: 'load-balancer-api-internal: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 14.231441ms
      message: 'load-balancer-api-internal: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 4.214991ms
      message: 'load-balancer-api-internal: tcp connection to a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:53:30Z"
    - latency: 6.844218ms
      message: 'load-balancer-api-internal: resolved host name a366fd53099b14fab8d6a30c93640430-6009dc9d1624128e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:45:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-175-to-network-check-target-ip-10-0-128-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-175.ec2.internal
      uid: e9c88479-9715-464a-953c-53c503ef4e24
    resourceVersion: "30099"
    uid: 907d3de7-3a42-4970-9410-5cedc55db696
  spec:
    sourcePod: network-check-source-56d84b9f44-27db7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:52:30Z"
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.712µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:30Z"
    - latency: 1.007962ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:30Z"
    - latency: 908.22µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 967.108µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 880.428µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 874.759µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 877.916µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:53:30Z"
    - latency: 1.57404ms
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:52:30Z"
    - latency: 994.71µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:51:30Z"
    - latency: 966.742µs
      message: 'network-check-target-ip-10-0-128-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:50:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:45:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-175-to-network-check-target-ip-10-0-129-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-175.ec2.internal
      uid: e9c88479-9715-464a-953c-53c503ef4e24
    resourceVersion: "30100"
    uid: dddae8be-0713-494b-86f9-073c45e3eb27
  spec:
    sourcePod: network-check-source-56d84b9f44-27db7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:52:30Z"
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.234536ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:30Z"
    - latency: 2.317273ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:30Z"
    - latency: 2.670105ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 2.427227ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 2.339682ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 2.032608ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 2.060493ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:53:30Z"
    - latency: 2.511877ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:52:30Z"
    - latency: 2.506664ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:51:30Z"
    - latency: 2.330572ms
      message: 'network-check-target-ip-10-0-129-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:50:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:45:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-175-to-network-check-target-ip-10-0-139-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-175.ec2.internal
      uid: e9c88479-9715-464a-953c-53c503ef4e24
    resourceVersion: "30101"
    uid: 603607f0-4336-44ae-952a-0dd83fc271c3
  spec:
    sourcePod: network-check-source-56d84b9f44-27db7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:52:30Z"
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.622846ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:59:30Z"
    - latency: 2.627622ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:58:30Z"
    - latency: 2.100778ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 2.232293ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 2.090204ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 2.41894ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 2.404054ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:53:30Z"
    - latency: 2.536908ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:52:30Z"
    - latency: 2.739709ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:51:30Z"
    - latency: 2.539657ms
      message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:50:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T15:45:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-175-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-175.ec2.internal
      uid: e9c88479-9715-464a-953c-53c503ef4e24
    resourceVersion: "28545"
    uid: 376d5c65-b767-4ec1-ae41-41c289907fe8
  spec:
    sourcePod: network-check-source-56d84b9f44-27db7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T15:51:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.892µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 1.675292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:57:30Z"
    - latency: 1.097655ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 1.776301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:56:30Z"
    - latency: 1.183948ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 1.769792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:55:30Z"
    - latency: 916.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 1.640042ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:54:30Z"
    - latency: 835.836µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T15:53:30Z"
    - latency: 1.763033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T15:53:30Z"
kind: List
metadata:
  resourceVersion: ""