apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-21.ec2.internal
      uid: 14902fb8-0479-4836-b3a2-b93bb0479062
    resourceVersion: "60527"
    uid: b172b108-8a7e-448e-972c-42e4c8745b48
  spec:
    sourcePod: network-check-source-869dcfcdcd-d7v2f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.077747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 1.246776ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 1.368613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 1.475521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 1.514416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:32:02Z"
    - latency: 3.425203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:31:02Z"
    - latency: 3.437372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:30:02Z"
    - latency: 1.342963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:29:02Z"
    - latency: 1.346797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:28:02Z"
    - latency: 847.467µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-21.ec2.internal
      uid: 14902fb8-0479-4836-b3a2-b93bb0479062
    resourceVersion: "60529"
    uid: 179d6833-37c9-40c6-a0e3-adaaa7cec0c4
  spec:
    sourcePod: network-check-source-869dcfcdcd-d7v2f
    targetEndpoint: a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:00:02Z"
      message: 'load-balancer-api-external: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.171442ms
      message: 'load-balancer-api-external: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 10.191543ms
      message: 'load-balancer-api-external: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 5.095977ms
      message: 'load-balancer-api-external: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 8.480972ms
      message: 'load-balancer-api-external: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 3.595533ms
      message: 'load-balancer-api-external: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 8.252762ms
      message: 'load-balancer-api-external: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 4.700428ms
      message: 'load-balancer-api-external: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 9.109433ms
      message: 'load-balancer-api-external: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 4.897988ms
      message: 'load-balancer-api-external: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:32:02Z"
    - latency: 8.127898ms
      message: 'load-balancer-api-external: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-21.ec2.internal
      uid: 14902fb8-0479-4836-b3a2-b93bb0479062
    resourceVersion: "60528"
    uid: 3ea95eae-596a-4a9e-84b1-7c853e55b8e9
  spec:
    sourcePod: network-check-source-869dcfcdcd-d7v2f
    targetEndpoint: a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:00:02Z"
      message: 'load-balancer-api-internal: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045311ms
      message: 'load-balancer-api-internal: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 10.263714ms
      message: 'load-balancer-api-internal: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 5.124958ms
      message: 'load-balancer-api-internal: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 8.464673ms
      message: 'load-balancer-api-internal: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 4.488987ms
      message: 'load-balancer-api-internal: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 8.385721ms
      message: 'load-balancer-api-internal: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 3.967703ms
      message: 'load-balancer-api-internal: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 9.162738ms
      message: 'load-balancer-api-internal: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 4.070861ms
      message: 'load-balancer-api-internal: tcp connection to a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:32:02Z"
    - latency: 8.145493ms
      message: 'load-balancer-api-internal: resolved host name a91fb1af45fab4948a282fa721fa1436-b8eb471c7bee5f8d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:32:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-21-to-network-check-target-ip-10-0-129-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-21.ec2.internal
      uid: 14902fb8-0479-4836-b3a2-b93bb0479062
    resourceVersion: "60523"
    uid: c90a1823-8f61-45a6-969e-a549e85e699f
  spec:
    sourcePod: network-check-source-869dcfcdcd-d7v2f
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:02Z"
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.081266ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 2.242903ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 2.066284ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 2.373219ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 2.189229ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:32:02Z"
    - latency: 2.754607ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:31:02Z"
    - latency: 6.880353ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:30:02Z"
    - latency: 2.471134ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:29:02Z"
    - latency: 2.165423ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:28:02Z"
    - latency: 1.964606ms
      message: 'network-check-target-ip-10-0-129-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-21-to-network-check-target-ip-10-0-133-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-21.ec2.internal
      uid: 14902fb8-0479-4836-b3a2-b93bb0479062
    resourceVersion: "60524"
    uid: efc328f6-6f47-4f68-ad98-af666bca85ce
  spec:
    sourcePod: network-check-source-869dcfcdcd-d7v2f
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:02Z"
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.702485ms
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 979.093µs
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 1.156435ms
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 2.219068ms
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 1.056999ms
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:32:02Z"
    - latency: 3.825358ms
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:31:02Z"
    - latency: 6.361151ms
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:30:02Z"
    - latency: 1.595152ms
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:29:02Z"
    - latency: 950.132µs
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:28:02Z"
    - latency: 979.171µs
      message: 'network-check-target-ip-10-0-133-21: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-21-to-network-check-target-ip-10-0-139-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-21.ec2.internal
      uid: 14902fb8-0479-4836-b3a2-b93bb0479062
    resourceVersion: "60522"
    uid: b6d02d09-4dbc-4b9f-8de4-903c6500c211
  spec:
    sourcePod: network-check-source-869dcfcdcd-d7v2f
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:01:02Z"
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345737ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 2.51466ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 2.274917ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 2.483147ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 2.034403ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:32:02Z"
    - latency: 2.910063ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:31:02Z"
    - latency: 3.432151ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:30:02Z"
    - latency: 2.449702ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:29:02Z"
    - latency: 2.148381ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:28:02Z"
    - latency: 2.383362ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:27:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T13:54:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-21.ec2.internal
      uid: 14902fb8-0479-4836-b3a2-b93bb0479062
    resourceVersion: "60525"
    uid: a3d63cf0-b573-4b90-a359-f2f657bf6c03
  spec:
    sourcePod: network-check-source-869dcfcdcd-d7v2f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:00:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.138429ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 2.684921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:36:02Z"
    - latency: 846.231µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 2.020987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:35:02Z"
    - latency: 892.299µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 1.910474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:34:02Z"
    - latency: 1.004005ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 2.496335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:33:02Z"
    - latency: 1.068929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T14:32:02Z"
    - latency: 2.208385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T14:32:02Z"
kind: List
metadata:
  resourceVersion: ""