apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T10:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 003b139e-3864-439f-905d-7a399f747b1b
    resourceVersion: "16900"
    uid: 2a9b2ec6-e183-4c09-a81f-9ec772756ba5
  spec:
    sourcePod: network-check-source-7cbc45fddc-v77g8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:03:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.413µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:10:07Z"
    - latency: 945.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:09:07Z"
    - latency: 990.461µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 932.684µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 1.20672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 890.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 958.678µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:04:07Z"
    - latency: 1.205439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:03:07Z"
    - latency: 910.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:02:07Z"
    - latency: 964.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T10:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 003b139e-3864-439f-905d-7a399f747b1b
    resourceVersion: "16125"
    uid: fde1ddf4-245e-4f0c-9b51-ebbec5cd9750
  spec:
    sourcePod: network-check-source-7cbc45fddc-v77g8
    targetEndpoint: a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:02:07Z"
      message: 'load-balancer-api-external: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.259391ms
      message: 'load-balancer-api-external: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 6.805289ms
      message: 'load-balancer-api-external: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 4.756365ms
      message: 'load-balancer-api-external: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 7.006976ms
      message: 'load-balancer-api-external: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 4.7118ms
      message: 'load-balancer-api-external: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 11.041339ms
      message: 'load-balancer-api-external: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 4.953975ms
      message: 'load-balancer-api-external: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 7.076639ms
      message: 'load-balancer-api-external: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 4.242177ms
      message: 'load-balancer-api-external: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:04:07Z"
    - latency: 7.185757ms
      message: 'load-balancer-api-external: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T10:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 003b139e-3864-439f-905d-7a399f747b1b
    resourceVersion: "16124"
    uid: 82994f07-9529-4a38-85d8-10958f36b27b
  spec:
    sourcePod: network-check-source-7cbc45fddc-v77g8
    targetEndpoint: a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:02:07Z"
      message: 'load-balancer-api-internal: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.380835ms
      message: 'load-balancer-api-internal: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 6.750916ms
      message: 'load-balancer-api-internal: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 5.237128ms
      message: 'load-balancer-api-internal: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 7.054697ms
      message: 'load-balancer-api-internal: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 6.119468ms
      message: 'load-balancer-api-internal: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 11.010126ms
      message: 'load-balancer-api-internal: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 4.93808ms
      message: 'load-balancer-api-internal: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 7.029159ms
      message: 'load-balancer-api-internal: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 4.240665ms
      message: 'load-balancer-api-internal: tcp connection to a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:04:07Z"
    - latency: 7.156281ms
      message: 'load-balancer-api-internal: resolved host name a8a428cb432074cef8f4789dbadea5c9-61aeee4f67ad2db8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:04:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T10:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-ip-10-0-131-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 003b139e-3864-439f-905d-7a399f747b1b
    resourceVersion: "16897"
    uid: 7f094583-0d6c-415a-b37c-ee554d2d702c
  spec:
    sourcePod: network-check-source-7cbc45fddc-v77g8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:03:07Z"
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.718303ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:10:07Z"
    - latency: 1.764136ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:09:07Z"
    - latency: 2.172625ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 2.114344ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 1.993864ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 2.043632ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 2.075205ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:04:07Z"
    - latency: 2.185778ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:03:07Z"
    - latency: 2.412141ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:02:07Z"
    - latency: 1.753241ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T10:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-ip-10-0-138-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 003b139e-3864-439f-905d-7a399f747b1b
    resourceVersion: "16899"
    uid: f3162439-c1ad-4c15-ab00-c2db5ff255e1
  spec:
    sourcePod: network-check-source-7cbc45fddc-v77g8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:03:07Z"
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.21156ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:10:07Z"
    - latency: 2.082488ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:09:07Z"
    - latency: 2.357001ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 2.75868ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 2.168289ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 2.157552ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 2.234811ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:04:07Z"
    - latency: 7.865368ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:03:07Z"
    - latency: 8.062136ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:02:07Z"
    - latency: 2.24457ms
      message: 'network-check-target-ip-10-0-138-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T10:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-ip-10-0-140-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 003b139e-3864-439f-905d-7a399f747b1b
    resourceVersion: "16898"
    uid: 503f515f-105d-443a-aba0-9d7a201460f5
  spec:
    sourcePod: network-check-source-7cbc45fddc-v77g8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:03:07Z"
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.366µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:10:07Z"
    - latency: 1.151812ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:09:07Z"
    - latency: 1.240879ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 1.055068ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 1.194907ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 1.257801ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 925.184µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:04:07Z"
    - latency: 1.400624ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:03:07Z"
    - latency: 1.230789ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:02:07Z"
    - latency: 764.18µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T10:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 003b139e-3864-439f-905d-7a399f747b1b
    resourceVersion: "16123"
    uid: ff337472-57f6-4e01-ab98-d1fc20cc038d
  spec:
    sourcePod: network-check-source-7cbc45fddc-v77g8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:02:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.83µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 1.677431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:08:07Z"
    - latency: 1.4377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 1.666145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:07:07Z"
    - latency: 920.303µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 1.957176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:06:07Z"
    - latency: 834.074µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 1.71718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:05:07Z"
    - latency: 1.073943ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:04:07Z"
    - latency: 1.828008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:04:07Z"
kind: List
metadata:
  resourceVersion: ""