apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:19:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-128.ec2.internal
      uid: e92ba69a-ebe4-45d7-a522-7446bca178d6
    resourceVersion: "54370"
    uid: b2e96493-3dd8-41f1-8072-3217491f4570
  spec:
    sourcePod: network-check-source-989f8b8dc-cjfvl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:26:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 1.178775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 1.246916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 1.316429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:53Z"
    - latency: 908.856µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:53Z"
    - latency: 1.147592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:53Z"
    - latency: 1.123384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:53Z"
    - latency: 1.206215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:53Z"
    - latency: 1.421874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:53Z"
    - latency: 852.74µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:19:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-128.ec2.internal
      uid: e92ba69a-ebe4-45d7-a522-7446bca178d6
    resourceVersion: "55377"
    uid: a5c29fae-0a94-4b98-a3f7-5eda2fb23e39
  spec:
    sourcePod: network-check-source-989f8b8dc-cjfvl
    targetEndpoint: a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:25:53Z"
      message: 'load-balancer-api-external: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.88312ms
      message: 'load-balancer-api-external: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:55:53Z"
    - latency: 21.231028ms
      message: 'load-balancer-api-external: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:55:53Z"
    - latency: 5.129124ms
      message: 'load-balancer-api-external: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 14.614525ms
      message: 'load-balancer-api-external: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 6.449714ms
      message: 'load-balancer-api-external: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 11.113935ms
      message: 'load-balancer-api-external: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 4.362092ms
      message: 'load-balancer-api-external: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 13.969838ms
      message: 'load-balancer-api-external: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 5.602376ms
      message: 'load-balancer-api-external: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:53Z"
    - latency: 11.749219ms
      message: 'load-balancer-api-external: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:51:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:19:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-128.ec2.internal
      uid: e92ba69a-ebe4-45d7-a522-7446bca178d6
    resourceVersion: "55376"
    uid: 0c2e2a30-1639-4d24-8709-92d03a86d586
  spec:
    sourcePod: network-check-source-989f8b8dc-cjfvl
    targetEndpoint: a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:25:53Z"
      message: 'load-balancer-api-internal: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.220182ms
      message: 'load-balancer-api-internal: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:55:53Z"
    - latency: 21.303007ms
      message: 'load-balancer-api-internal: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:55:53Z"
    - latency: 5.129165ms
      message: 'load-balancer-api-internal: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 14.547489ms
      message: 'load-balancer-api-internal: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 6.388732ms
      message: 'load-balancer-api-internal: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 11.244197ms
      message: 'load-balancer-api-internal: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 4.30965ms
      message: 'load-balancer-api-internal: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 13.998606ms
      message: 'load-balancer-api-internal: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 4.485027ms
      message: 'load-balancer-api-internal: tcp connection to a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:53Z"
    - latency: 11.695911ms
      message: 'load-balancer-api-internal: resolved host name a286dc310cac1496e9864443dbda47b8-32528262df257f11.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:51:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:19:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-128-to-network-check-target-ip-10-0-131-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-128.ec2.internal
      uid: e92ba69a-ebe4-45d7-a522-7446bca178d6
    resourceVersion: "54367"
    uid: 9739ed4c-87bf-4520-96d0-864ef4407fe8
  spec:
    sourcePod: network-check-source-989f8b8dc-cjfvl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:26:53Z"
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.624µs
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 874.948µs
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 1.083241ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 909.183µs
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:53Z"
    - latency: 696.58µs
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:53Z"
    - latency: 1.036594ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:53Z"
    - latency: 870.351µs
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:53Z"
    - latency: 883.688µs
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:53Z"
    - latency: 1.039255ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:53Z"
    - latency: 729.136µs
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:19:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-128-to-network-check-target-ip-10-0-133-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-128.ec2.internal
      uid: e92ba69a-ebe4-45d7-a522-7446bca178d6
    resourceVersion: "54368"
    uid: 33518dba-b0ed-4569-b634-27c3838e510b
  spec:
    sourcePod: network-check-source-989f8b8dc-cjfvl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:26:53Z"
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.637234ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 2.012515ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 1.85841ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 1.977547ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:53Z"
    - latency: 1.862461ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:53Z"
    - latency: 1.849221ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:53Z"
    - latency: 1.910696ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:53Z"
    - latency: 2.017879ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:53Z"
    - latency: 1.779637ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:53Z"
    - latency: 1.707239ms
      message: 'network-check-target-ip-10-0-133-157: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:19:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-128-to-network-check-target-ip-10-0-133-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-128.ec2.internal
      uid: e92ba69a-ebe4-45d7-a522-7446bca178d6
    resourceVersion: "54369"
    uid: fd94ee4a-8d97-46b5-a3d8-c34e7f085930
  spec:
    sourcePod: network-check-source-989f8b8dc-cjfvl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:26:53Z"
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.034718ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 2.057635ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 1.983478ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 2.120373ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:53Z"
    - latency: 2.259336ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:50:53Z"
    - latency: 2.08012ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:49:53Z"
    - latency: 2.098656ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:48:53Z"
    - latency: 2.024322ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:47:53Z"
    - latency: 2.050787ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:46:53Z"
    - latency: 1.847138ms
      message: 'network-check-target-ip-10-0-133-20: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:45:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T13:19:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-128.ec2.internal
      uid: e92ba69a-ebe4-45d7-a522-7446bca178d6
    resourceVersion: "55375"
    uid: e3dff675-0d44-4cba-9dd5-f4552b6db77b
  spec:
    sourcePod: network-check-source-989f8b8dc-cjfvl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T13:25:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.937µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:55:53Z"
    - latency: 1.766043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:55:53Z"
    - latency: 965.89µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 1.715262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:54:53Z"
    - latency: 922.923µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 2.443241ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:53:53Z"
    - latency: 914.982µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 1.814463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:52:53Z"
    - latency: 1.025942ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T13:51:53Z"
    - latency: 1.807037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T13:51:53Z"
kind: List
metadata:
  resourceVersion: ""