apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-215.ec2.internal
      uid: 7a345fd7-6643-47f7-9f1c-91136d187630
    resourceVersion: "83134"
    uid: 11b85941-1f5f-4277-9cbd-ba8a4a163ece
  spec:
    sourcePod: network-check-source-869dcfcdcd-jfqf9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:01:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.086202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:39Z"
    - latency: 1.207181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:39Z"
    - latency: 1.321497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:39Z"
    - latency: 1.173095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:39Z"
    - latency: 1.456662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:39Z"
    - latency: 896.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:39Z"
    - latency: 1.169962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:39Z"
    - latency: 1.466781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:39Z"
    - latency: 1.233877ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:39Z"
    - latency: 801.843µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-215.ec2.internal
      uid: 7a345fd7-6643-47f7-9f1c-91136d187630
    resourceVersion: "87394"
    uid: 8db731b7-0dcd-4d79-9b5b-b52da4cb7eb7
  spec:
    sourcePod: network-check-source-869dcfcdcd-jfqf9
    targetEndpoint: a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:00:39Z"
      message: 'load-balancer-api-external: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.114799ms
      message: 'load-balancer-api-external: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:24:39Z"
    - latency: 7.221906ms
      message: 'load-balancer-api-external: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:24:39Z"
    - latency: 3.592276ms
      message: 'load-balancer-api-external: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:23:39Z"
    - latency: 13.092019ms
      message: 'load-balancer-api-external: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:23:39Z"
    - latency: 3.785388ms
      message: 'load-balancer-api-external: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:22:39Z"
    - latency: 6.703308ms
      message: 'load-balancer-api-external: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:22:39Z"
    - latency: 14.292775ms
      message: 'load-balancer-api-external: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:21:39Z"
    - latency: 6.797196ms
      message: 'load-balancer-api-external: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:21:39Z"
    - latency: 4.980356ms
      message: 'load-balancer-api-external: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:20:39Z"
    - latency: 6.828137ms
      message: 'load-balancer-api-external: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:20:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-215.ec2.internal
      uid: 7a345fd7-6643-47f7-9f1c-91136d187630
    resourceVersion: "87395"
    uid: 3a304b13-0f4c-49a0-b757-d0ea7f640d5b
  spec:
    sourcePod: network-check-source-869dcfcdcd-jfqf9
    targetEndpoint: a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:00:39Z"
      message: 'load-balancer-api-internal: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.261797ms
      message: 'load-balancer-api-internal: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:24:39Z"
    - latency: 7.158629ms
      message: 'load-balancer-api-internal: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:24:39Z"
    - latency: 4.132853ms
      message: 'load-balancer-api-internal: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:23:39Z"
    - latency: 13.121809ms
      message: 'load-balancer-api-internal: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:23:39Z"
    - latency: 3.804195ms
      message: 'load-balancer-api-internal: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:22:39Z"
    - latency: 6.685614ms
      message: 'load-balancer-api-internal: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:22:39Z"
    - latency: 4.277213ms
      message: 'load-balancer-api-internal: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:21:39Z"
    - latency: 6.832689ms
      message: 'load-balancer-api-internal: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:21:39Z"
    - latency: 4.419593ms
      message: 'load-balancer-api-internal: tcp connection to a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:20:39Z"
    - latency: 6.849154ms
      message: 'load-balancer-api-internal: resolved host name a3cde18be540944adbcbe5b2ee93881c-9d3d79d2762ce307.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:20:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-215-to-network-check-target-ip-10-0-128-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-215.ec2.internal
      uid: 7a345fd7-6643-47f7-9f1c-91136d187630
    resourceVersion: "83130"
    uid: 2a55b492-b8cc-4175-ba8b-43b672e37e16
  spec:
    sourcePod: network-check-source-869dcfcdcd-jfqf9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:01:39Z"
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.385827ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:39Z"
    - latency: 826.856µs
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:39Z"
    - latency: 948.266µs
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:39Z"
    - latency: 1.228395ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:39Z"
    - latency: 824.453µs
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:39Z"
    - latency: 1.171358ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:39Z"
    - latency: 812.132µs
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:39Z"
    - latency: 1.255496ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:39Z"
    - latency: 1.386672ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:39Z"
    - latency: 1.39171ms
      message: 'network-check-target-ip-10-0-128-215: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-215-to-network-check-target-ip-10-0-131-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-215.ec2.internal
      uid: 7a345fd7-6643-47f7-9f1c-91136d187630
    resourceVersion: "83132"
    uid: 7e5f8615-d0ea-4587-9fd8-9be7cd3269db
  spec:
    sourcePod: network-check-source-869dcfcdcd-jfqf9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:01:39Z"
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275615ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:39Z"
    - latency: 2.851318ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:39Z"
    - latency: 2.244292ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:39Z"
    - latency: 2.129803ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:39Z"
    - latency: 2.260394ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:39Z"
    - latency: 2.026645ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:39Z"
    - latency: 1.93639ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:39Z"
    - latency: 2.612771ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:39Z"
    - latency: 2.309269ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:39Z"
    - latency: 1.998904ms
      message: 'network-check-target-ip-10-0-131-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-215-to-network-check-target-ip-10-0-139-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-215.ec2.internal
      uid: 7a345fd7-6643-47f7-9f1c-91136d187630
    resourceVersion: "83131"
    uid: 49406e24-4b3b-43ae-958b-bb0e1db6ff53
  spec:
    sourcePod: network-check-source-869dcfcdcd-jfqf9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:01:39Z"
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.220138ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:18:39Z"
    - latency: 1.838231ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:17:39Z"
    - latency: 1.761613ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:16:39Z"
    - latency: 2.277656ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:15:39Z"
    - latency: 1.934602ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:14:39Z"
    - latency: 1.984626ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:13:39Z"
    - latency: 1.9477ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:12:39Z"
    - latency: 2.149332ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:11:39Z"
    - latency: 1.737914ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:10:39Z"
    - latency: 2.082976ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:09:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T18:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-215.ec2.internal
      uid: 7a345fd7-6643-47f7-9f1c-91136d187630
    resourceVersion: "87393"
    uid: 08a8cf27-04dc-4703-b653-d8e89db7832d
  spec:
    sourcePod: network-check-source-869dcfcdcd-jfqf9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:00:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.836µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:24:39Z"
    - latency: 1.869384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:24:39Z"
    - latency: 941.817µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:23:39Z"
    - latency: 1.768331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:23:39Z"
    - latency: 831.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:22:39Z"
    - latency: 1.755347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:22:39Z"
    - latency: 1.062597ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:21:39Z"
    - latency: 1.693675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:21:39Z"
    - latency: 939.693µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:20:39Z"
    - latency: 1.795788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:20:39Z"
kind: List
metadata:
  resourceVersion: ""