apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T22:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 7bbcf8ba-964a-442a-a94f-2116fbcd589d
    resourceVersion: "16985"
    uid: de9a638e-7baf-4dad-a1f6-55824baf4268
  spec:
    sourcePod: network-check-source-869dcfcdcd-6rfxl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:30:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.106747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:37:16Z"
    - latency: 1.039737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:16Z"
    - latency: 1.522682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 1.071489ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 1.128901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 980.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 1.119208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:16Z"
    - latency: 1.014552ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:16Z"
    - latency: 947.699µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:16Z"
    - latency: 1.002838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T22:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 7bbcf8ba-964a-442a-a94f-2116fbcd589d
    resourceVersion: "16224"
    uid: e58dbc8c-20c6-4829-a908-5512bf6b8000
  spec:
    sourcePod: network-check-source-869dcfcdcd-6rfxl
    targetEndpoint: a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:29:16Z"
      message: 'load-balancer-api-external: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.30137ms
      message: 'load-balancer-api-external: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 7.904597ms
      message: 'load-balancer-api-external: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 5.59433ms
      message: 'load-balancer-api-external: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 8.107244ms
      message: 'load-balancer-api-external: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 3.5902ms
      message: 'load-balancer-api-external: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 9.055461ms
      message: 'load-balancer-api-external: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 5.290336ms
      message: 'load-balancer-api-external: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 7.506268ms
      message: 'load-balancer-api-external: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 5.170487ms
      message: 'load-balancer-api-external: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:16Z"
    - latency: 14.046389ms
      message: 'load-balancer-api-external: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:31:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T22:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 7bbcf8ba-964a-442a-a94f-2116fbcd589d
    resourceVersion: "16225"
    uid: 5f1dc9bf-4ff0-4914-8e8c-3f8cb9b44ce6
  spec:
    sourcePod: network-check-source-869dcfcdcd-6rfxl
    targetEndpoint: a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:29:16Z"
      message: 'load-balancer-api-internal: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.791912ms
      message: 'load-balancer-api-internal: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 7.809014ms
      message: 'load-balancer-api-internal: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 5.569683ms
      message: 'load-balancer-api-internal: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 8.053753ms
      message: 'load-balancer-api-internal: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 4.960725ms
      message: 'load-balancer-api-internal: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 9.107858ms
      message: 'load-balancer-api-internal: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 5.300444ms
      message: 'load-balancer-api-internal: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 7.558003ms
      message: 'load-balancer-api-internal: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 5.163438ms
      message: 'load-balancer-api-internal: tcp connection to a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:16Z"
    - latency: 14.019114ms
      message: 'load-balancer-api-internal: resolved host name a69010c06d30140ccaa30a6c3753e73d-9dd1c9577991a144.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:31:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T22:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-ip-10-0-135-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 7bbcf8ba-964a-442a-a94f-2116fbcd589d
    resourceVersion: "16983"
    uid: 6c8b2812-661e-4be3-baea-d3257f5b7bd0
  spec:
    sourcePod: network-check-source-869dcfcdcd-6rfxl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:30:16Z"
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.229447ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:37:16Z"
    - latency: 2.076051ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:16Z"
    - latency: 2.219836ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 1.873153ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 2.747437ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 2.427061ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 2.116189ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:16Z"
    - latency: 2.266638ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:16Z"
    - latency: 1.829374ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:16Z"
    - latency: 2.138445ms
      message: 'network-check-target-ip-10-0-135-224: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T22:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-ip-10-0-139-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 7bbcf8ba-964a-442a-a94f-2116fbcd589d
    resourceVersion: "16984"
    uid: 8969e545-dda1-4f72-8d1a-9a07e6355d68
  spec:
    sourcePod: network-check-source-869dcfcdcd-6rfxl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:30:16Z"
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.202153ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:37:16Z"
    - latency: 2.241132ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:16Z"
    - latency: 2.537257ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 1.940832ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 2.092365ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 2.463056ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 2.362839ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:16Z"
    - latency: 2.170457ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:16Z"
    - latency: 2.135521ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:16Z"
    - latency: 2.137565ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T22:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-ip-10-0-143-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 7bbcf8ba-964a-442a-a94f-2116fbcd589d
    resourceVersion: "16982"
    uid: f3cacd57-6bd2-4cb1-b3ae-6b8995566ac2
  spec:
    sourcePod: network-check-source-869dcfcdcd-6rfxl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:30:16Z"
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.817µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:37:16Z"
    - latency: 1.384964ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:36:16Z"
    - latency: 1.780159ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 902.236µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 1.336875ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 1.128851ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 903.609µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:16Z"
    - latency: 951.805µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:30:16Z"
    - latency: 935.004µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:29:16Z"
    - latency: 875.666µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:28:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T22:23:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 7bbcf8ba-964a-442a-a94f-2116fbcd589d
    resourceVersion: "16223"
    uid: 609e37cd-2286-4d5b-a195-9d654ee8ba27
  spec:
    sourcePod: network-check-source-869dcfcdcd-6rfxl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T22:29:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 791.48µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 1.832681ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:35:16Z"
    - latency: 1.179139ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 1.770855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:34:16Z"
    - latency: 1.242075ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 1.875312ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:33:16Z"
    - latency: 845.097µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 1.848051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:32:16Z"
    - latency: 1.335464ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T22:31:16Z"
    - latency: 1.816819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T22:31:16Z"
kind: List
metadata:
  resourceVersion: ""