apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-39-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-39.ec2.internal
      uid: 563fccc8-f121-4400-8a4f-ea4c73af5281
    resourceVersion: "68609"
    uid: 4981fcb9-a7d5-4112-ab08-8bbe34dd70c8
  spec:
    sourcePod: network-check-source-7cbc45fddc-g6wht
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:01Z"
    - latency: 1.230315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:01Z"
    - latency: 3.629125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:01Z"
    - latency: 1.148981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:01Z"
    - latency: 1.38187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:01Z"
    - latency: 2.093682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:01Z"
    - latency: 1.191153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:01Z"
    - latency: 1.191082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:01Z"
    - latency: 3.051158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:01Z"
    - latency: 1.25171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-39-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-39.ec2.internal
      uid: 563fccc8-f121-4400-8a4f-ea4c73af5281
    resourceVersion: "73116"
    uid: 123e3807-85a2-42ea-ad45-25f3ab25c591
  spec:
    sourcePod: network-check-source-7cbc45fddc-g6wht
    targetEndpoint: a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:01Z"
      message: 'load-balancer-api-external: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.682956ms
      message: 'load-balancer-api-external: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:01Z"
    - latency: 9.233555ms
      message: 'load-balancer-api-external: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:44:01Z"
    - latency: 3.327891ms
      message: 'load-balancer-api-external: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:01Z"
    - latency: 7.162103ms
      message: 'load-balancer-api-external: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:43:01Z"
    - latency: 5.056825ms
      message: 'load-balancer-api-external: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:01Z"
    - latency: 7.762825ms
      message: 'load-balancer-api-external: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:42:01Z"
    - latency: 4.751189ms
      message: 'load-balancer-api-external: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:01Z"
    - latency: 10.376828ms
      message: 'load-balancer-api-external: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:41:01Z"
    - latency: 5.773402ms
      message: 'load-balancer-api-external: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:01Z"
    - latency: 10.161777ms
      message: 'load-balancer-api-external: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:40:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-39-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-39.ec2.internal
      uid: 563fccc8-f121-4400-8a4f-ea4c73af5281
    resourceVersion: "73115"
    uid: 8e621e0b-f4d8-44f3-a745-18f8f2e3bf56
  spec:
    sourcePod: network-check-source-7cbc45fddc-g6wht
    targetEndpoint: a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:01Z"
      message: 'load-balancer-api-internal: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.001584ms
      message: 'load-balancer-api-internal: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:01Z"
    - latency: 9.294969ms
      message: 'load-balancer-api-internal: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:44:01Z"
    - latency: 3.360989ms
      message: 'load-balancer-api-internal: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:01Z"
    - latency: 7.003219ms
      message: 'load-balancer-api-internal: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:43:01Z"
    - latency: 4.598827ms
      message: 'load-balancer-api-internal: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:01Z"
    - latency: 7.667563ms
      message: 'load-balancer-api-internal: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:42:01Z"
    - latency: 5.10818ms
      message: 'load-balancer-api-internal: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:01Z"
    - latency: 10.514033ms
      message: 'load-balancer-api-internal: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:41:01Z"
    - latency: 5.822002ms
      message: 'load-balancer-api-internal: tcp connection to a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:01Z"
    - latency: 10.346437ms
      message: 'load-balancer-api-internal: resolved host name a3995170ec33944309497dbc5040364d-793b8c5c358b5692.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:40:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-39-to-network-check-target-ip-10-0-129-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-39.ec2.internal
      uid: 563fccc8-f121-4400-8a4f-ea4c73af5281
    resourceVersion: "68607"
    uid: ca449bf3-2d41-473d-97e6-2f80eb0ec8c9
  spec:
    sourcePod: network-check-source-7cbc45fddc-g6wht
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:01Z"
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.087785ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:01Z"
    - latency: 2.682913ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:01Z"
    - latency: 2.610328ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:01Z"
    - latency: 2.157032ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:01Z"
    - latency: 2.264956ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:01Z"
    - latency: 2.350075ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:01Z"
    - latency: 2.116414ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:01Z"
    - latency: 2.6702ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:01Z"
    - latency: 2.599327ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:01Z"
    - latency: 2.021187ms
      message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-39-to-network-check-target-ip-10-0-139-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-39.ec2.internal
      uid: 563fccc8-f121-4400-8a4f-ea4c73af5281
    resourceVersion: "68606"
    uid: 2823e0f9-1f6e-4be8-b89e-9836399e786d
  spec:
    sourcePod: network-check-source-7cbc45fddc-g6wht
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:01Z"
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.758µs
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:01Z"
    - latency: 924.28µs
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:01Z"
    - latency: 4.306061ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:01Z"
    - latency: 747.409µs
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:01Z"
    - latency: 1.365166ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:01Z"
    - latency: 3.525859ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:01Z"
    - latency: 1.263234ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:01Z"
    - latency: 1.499232ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:01Z"
    - latency: 2.489482ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:01Z"
    - latency: 802.203µs
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-39-to-network-check-target-ip-10-0-142-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-39.ec2.internal
      uid: 563fccc8-f121-4400-8a4f-ea4c73af5281
    resourceVersion: "68608"
    uid: b5d2995d-6d16-411e-a1b2-fd66c50595a7
  spec:
    sourcePod: network-check-source-7cbc45fddc-g6wht
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:51:01Z"
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.50705ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:01Z"
    - latency: 2.306883ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:01Z"
    - latency: 2.293828ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:01Z"
    - latency: 2.069715ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:01Z"
    - latency: 2.248287ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:01Z"
    - latency: 3.13048ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:01Z"
    - latency: 2.406785ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:01Z"
    - latency: 2.294137ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:01Z"
    - latency: 3.151079ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:01Z"
    - latency: 2.162968ms
      message: 'network-check-target-ip-10-0-142-71: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:31:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:44:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-39-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-39.ec2.internal
      uid: 563fccc8-f121-4400-8a4f-ea4c73af5281
    resourceVersion: "73113"
    uid: dca47339-ff12-4783-a4f1-02c4f8dca8aa
  spec:
    sourcePod: network-check-source-7cbc45fddc-g6wht
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:50:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.491µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:44:01Z"
    - latency: 1.961746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:44:01Z"
    - latency: 869.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:43:01Z"
    - latency: 2.34082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:43:01Z"
    - latency: 1.025055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:42:01Z"
    - latency: 2.006191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:42:01Z"
    - latency: 1.092713ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:01Z"
    - latency: 1.903459ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:41:01Z"
    - latency: 1.005464ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:01Z"
    - latency: 1.704438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:40:01Z"
kind: List
metadata:
  resourceVersion: ""