apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: e079aa03-8175-404f-bbb7-6e33e78c222c
    resourceVersion: "74368"
    uid: 0a1f488c-5276-437f-b9ff-c73751ee09fc
  spec:
    sourcePod: network-check-source-7d88cb55d8-z72h7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:01:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.236µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:20Z"
    - latency: 1.395452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 1.027096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 841.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 1.394979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 1.493892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:20Z"
    - latency: 1.111236ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:20Z"
    - latency: 1.012741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:20Z"
    - latency: 865.971µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:20Z"
    - latency: 974.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: e079aa03-8175-404f-bbb7-6e33e78c222c
    resourceVersion: "72270"
    uid: 5a5869f6-1609-42d0-b0cb-1011485a9149
  spec:
    sourcePod: network-check-source-7d88cb55d8-z72h7
    targetEndpoint: ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:00:20Z"
      message: 'load-balancer-api-external: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.063197ms
      message: 'load-balancer-api-external: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 6.778423ms
      message: 'load-balancer-api-external: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 3.74992ms
      message: 'load-balancer-api-external: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 6.263157ms
      message: 'load-balancer-api-external: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 6.250341ms
      message: 'load-balancer-api-external: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 6.174815ms
      message: 'load-balancer-api-external: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 5.693684ms
      message: 'load-balancer-api-external: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 6.220475ms
      message: 'load-balancer-api-external: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 3.772026ms
      message: 'load-balancer-api-external: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:20Z"
    - latency: 6.689049ms
      message: 'load-balancer-api-external: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:38:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: e079aa03-8175-404f-bbb7-6e33e78c222c
    resourceVersion: "72269"
    uid: 607afd8d-e12a-46e2-8449-f5d68b3ff400
  spec:
    sourcePod: network-check-source-7d88cb55d8-z72h7
    targetEndpoint: ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:00:20Z"
      message: 'load-balancer-api-internal: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.095267ms
      message: 'load-balancer-api-internal: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 6.849704ms
      message: 'load-balancer-api-internal: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 5.52513ms
      message: 'load-balancer-api-internal: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 6.189891ms
      message: 'load-balancer-api-internal: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 6.263921ms
      message: 'load-balancer-api-internal: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 6.240715ms
      message: 'load-balancer-api-internal: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 3.64056ms
      message: 'load-balancer-api-internal: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 6.263799ms
      message: 'load-balancer-api-internal: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 3.870691ms
      message: 'load-balancer-api-internal: tcp connection to ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:20Z"
    - latency: 6.778259ms
      message: 'load-balancer-api-internal: resolved host name ab2d2f57852754de29b386fb7debe79e-95203513e4dbc283.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:38:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-131-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: e079aa03-8175-404f-bbb7-6e33e78c222c
    resourceVersion: "74363"
    uid: a4fa9fba-938b-4cac-82f9-46fbbfcb7b48
  spec:
    sourcePod: network-check-source-7d88cb55d8-z72h7
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:01:20Z"
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.679µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:20Z"
    - latency: 810.525µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 735.891µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 882.295µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 929.183µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 1.097633ms
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:20Z"
    - latency: 848.488µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:20Z"
    - latency: 942.543µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:20Z"
    - latency: 850.183µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:20Z"
    - latency: 868.788µs
      message: 'network-check-target-ip-10-0-131-232: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-131-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: e079aa03-8175-404f-bbb7-6e33e78c222c
    resourceVersion: "74364"
    uid: 91b03020-e406-4d9d-b374-8a257e1ea927
  spec:
    sourcePod: network-check-source-7d88cb55d8-z72h7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:01:20Z"
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.958498ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:20Z"
    - latency: 2.104632ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 2.0659ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 2.02184ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 2.120316ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 2.04698ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:20Z"
    - latency: 1.907373ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:20Z"
    - latency: 1.570126ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:20Z"
    - latency: 2.144384ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:20Z"
    - latency: 2.375508ms
      message: 'network-check-target-ip-10-0-131-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-ip-10-0-141-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: e079aa03-8175-404f-bbb7-6e33e78c222c
    resourceVersion: "74365"
    uid: 0f799e9f-e6c1-4f5e-a93a-5f8a4a84da2d
  spec:
    sourcePod: network-check-source-7d88cb55d8-z72h7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:01:20Z"
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.510001ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:43:20Z"
    - latency: 2.450838ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 2.735674ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 2.40154ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 3.093133ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 2.393538ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:20Z"
    - latency: 2.229553ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:37:20Z"
    - latency: 2.080037ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:36:20Z"
    - latency: 2.526017ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:35:20Z"
    - latency: 2.559126ms
      message: 'network-check-target-ip-10-0-141-50: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T20:54:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-232-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-232.ec2.internal
      uid: e079aa03-8175-404f-bbb7-6e33e78c222c
    resourceVersion: "72268"
    uid: c6bdbb7b-a40d-4929-ad2d-40b01b0de920
  spec:
    sourcePod: network-check-source-7d88cb55d8-z72h7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T21:00:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.451µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 1.710854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:42:20Z"
    - latency: 1.038911ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 1.836064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:41:20Z"
    - latency: 991.711µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 1.665113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:40:20Z"
    - latency: 1.249168ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 2.020871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:39:20Z"
    - latency: 1.008671ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T21:38:20Z"
    - latency: 1.737524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T21:38:20Z"
kind: List
metadata:
  resourceVersion: ""