apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-140-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-140.ec2.internal
      uid: e32444c0-7bfd-492e-8f4f-dcd0f8d39b63
    resourceVersion: "62060"
    uid: f6887738-88d5-400c-9cf5-623563a01d47
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6k5t4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.310332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 1.034428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 1.342981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 925.551µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 1.019409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:06Z"
    - latency: 905.917µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:06Z"
    - latency: 828.783µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:06Z"
    - latency: 1.618554ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:06Z"
    - latency: 1.022287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:06Z"
    - latency: 1.054403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-140-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-140.ec2.internal
      uid: e32444c0-7bfd-492e-8f4f-dcd0f8d39b63
    resourceVersion: "62062"
    uid: 31b5dd5f-e769-4edb-a5ae-52b3f26316fd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6k5t4
    targetEndpoint: a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:31:06Z"
      message: 'load-balancer-api-external: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.483632ms
      message: 'load-balancer-api-external: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 9.632608ms
      message: 'load-balancer-api-external: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 3.718054ms
      message: 'load-balancer-api-external: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 9.309016ms
      message: 'load-balancer-api-external: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 4.880788ms
      message: 'load-balancer-api-external: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 8.137965ms
      message: 'load-balancer-api-external: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 4.037221ms
      message: 'load-balancer-api-external: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 8.172662ms
      message: 'load-balancer-api-external: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 3.518752ms
      message: 'load-balancer-api-external: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:06Z"
    - latency: 8.038362ms
      message: 'load-balancer-api-external: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:03:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-140-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-140.ec2.internal
      uid: e32444c0-7bfd-492e-8f4f-dcd0f8d39b63
    resourceVersion: "62061"
    uid: 58ba6414-c597-4cc6-8193-6f37291f6c8e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6k5t4
    targetEndpoint: a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:31:06Z"
      message: 'load-balancer-api-internal: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.423027ms
      message: 'load-balancer-api-internal: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 9.662465ms
      message: 'load-balancer-api-internal: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 3.712285ms
      message: 'load-balancer-api-internal: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 9.487213ms
      message: 'load-balancer-api-internal: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 4.800758ms
      message: 'load-balancer-api-internal: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 8.229396ms
      message: 'load-balancer-api-internal: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 4.34888ms
      message: 'load-balancer-api-internal: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 8.236504ms
      message: 'load-balancer-api-internal: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 3.737539ms
      message: 'load-balancer-api-internal: tcp connection to a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:06Z"
    - latency: 8.184213ms
      message: 'load-balancer-api-internal: resolved host name a6377659f474841479464a2e7a8b6df1-e73ec76ff3f627c4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:03:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-140-to-network-check-target-ip-10-0-133-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-140.ec2.internal
      uid: e32444c0-7bfd-492e-8f4f-dcd0f8d39b63
    resourceVersion: "62059"
    uid: 94b3d252-f3fa-4f8d-b9f3-a27c1d1a4bba
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6k5t4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:06Z"
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.312597ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 2.442302ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 2.417931ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 2.689462ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 2.388349ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:06Z"
    - latency: 2.112598ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:06Z"
    - latency: 2.281029ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:06Z"
    - latency: 2.206963ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:06Z"
    - latency: 2.415885ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:06Z"
    - latency: 2.169918ms
      message: 'network-check-target-ip-10-0-133-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-140-to-network-check-target-ip-10-0-136-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-140.ec2.internal
      uid: e32444c0-7bfd-492e-8f4f-dcd0f8d39b63
    resourceVersion: "62056"
    uid: db5b525d-c39a-4146-9749-b975a546a911
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6k5t4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:06Z"
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.379495ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 1.453688ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 1.172782ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 1.486505ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 1.033578ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:06Z"
    - latency: 844.797µs
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:06Z"
    - latency: 1.324666ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:06Z"
    - latency: 882.687µs
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:06Z"
    - latency: 854.762µs
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:06Z"
    - latency: 1.262057ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-140-to-network-check-target-ip-10-0-143-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-140.ec2.internal
      uid: e32444c0-7bfd-492e-8f4f-dcd0f8d39b63
    resourceVersion: "62057"
    uid: 21a68fd3-8d14-4bef-a481-91130beda7a8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6k5t4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:32:06Z"
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.484694ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 2.378855ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 2.176147ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 2.678348ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 2.227392ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:06Z"
    - latency: 2.066726ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:02:06Z"
    - latency: 2.221355ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:01:06Z"
    - latency: 2.170589ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:00:06Z"
    - latency: 2.346325ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:59:06Z"
    - latency: 2.079781ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:58:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:25:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-140-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-140.ec2.internal
      uid: e32444c0-7bfd-492e-8f4f-dcd0f8d39b63
    resourceVersion: "62058"
    uid: 2e6d6c56-5c7a-41dc-8618-67b1fdda9d96
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6k5t4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:31:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.78µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 2.237668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:07:06Z"
    - latency: 872.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 2.283586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:06:06Z"
    - latency: 780.266µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 1.770239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:05:06Z"
    - latency: 1.073505ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 1.565394ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:04:06Z"
    - latency: 753.144µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T17:03:06Z"
    - latency: 1.685247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T17:03:06Z"
kind: List
metadata:
  resourceVersion: ""