apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-221-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-221.ec2.internal
      uid: 7b7186da-3f70-4145-b139-836b361f1795
    resourceVersion: "32585"
    uid: 60d57ac4-8125-4535-a352-539d030a2030
  spec:
    sourcePod: network-check-source-7cbc45fddc-d4tvc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:07:58Z"
    - latency: 1.419701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 1.664105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 1.249246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 832.897µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 1.124304ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:58Z"
    - latency: 1.2639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:58Z"
    - latency: 1.191898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:58Z"
    - latency: 1.414949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:58Z"
    - latency: 1.255925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-221-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-221.ec2.internal
      uid: 7b7186da-3f70-4145-b139-836b361f1795
    resourceVersion: "32207"
    uid: ef201ac4-df8d-4d47-816e-469f8b0961e9
  spec:
    sourcePod: network-check-source-7cbc45fddc-d4tvc
    targetEndpoint: ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:24:58Z"
      message: 'load-balancer-api-external: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.901199ms
      message: 'load-balancer-api-external: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 8.774061ms
      message: 'load-balancer-api-external: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 7.084184ms
      message: 'load-balancer-api-external: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 7.874497ms
      message: 'load-balancer-api-external: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 4.366433ms
      message: 'load-balancer-api-external: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 8.119238ms
      message: 'load-balancer-api-external: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 4.171059ms
      message: 'load-balancer-api-external: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 9.224851ms
      message: 'load-balancer-api-external: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 6.376773ms
      message: 'load-balancer-api-external: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:58Z"
    - latency: 8.369978ms
      message: 'load-balancer-api-external: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-221-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-221.ec2.internal
      uid: 7b7186da-3f70-4145-b139-836b361f1795
    resourceVersion: "32208"
    uid: a8067b82-e228-4389-8c67-25253644f000
  spec:
    sourcePod: network-check-source-7cbc45fddc-d4tvc
    targetEndpoint: ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:24:58Z"
      message: 'load-balancer-api-internal: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.91819ms
      message: 'load-balancer-api-internal: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 8.74551ms
      message: 'load-balancer-api-internal: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 6.987293ms
      message: 'load-balancer-api-internal: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 7.997793ms
      message: 'load-balancer-api-internal: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 4.292569ms
      message: 'load-balancer-api-internal: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 8.214244ms
      message: 'load-balancer-api-internal: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 4.169173ms
      message: 'load-balancer-api-internal: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 9.191342ms
      message: 'load-balancer-api-internal: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 6.459315ms
      message: 'load-balancer-api-internal: tcp connection to ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:58Z"
    - latency: 8.319143ms
      message: 'load-balancer-api-internal: resolved host name ab29de5512f1349a78cddc89ac81729b-68a038272dcba3dd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-221-to-network-check-target-ip-10-0-131-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-221.ec2.internal
      uid: 7b7186da-3f70-4145-b139-836b361f1795
    resourceVersion: "32582"
    uid: aefe19d9-c683-4993-807d-ba908712d2e1
  spec:
    sourcePod: network-check-source-7cbc45fddc-d4tvc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:58Z"
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.77µs
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:07:58Z"
    - latency: 1.354876ms
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 1.270198ms
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 1.36639ms
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 913.505µs
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 795.365µs
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:58Z"
    - latency: 807.925µs
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:58Z"
    - latency: 922.966µs
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:58Z"
    - latency: 1.052137ms
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:58Z"
    - latency: 963.421µs
      message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-221-to-network-check-target-ip-10-0-135-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-221.ec2.internal
      uid: 7b7186da-3f70-4145-b139-836b361f1795
    resourceVersion: "32584"
    uid: e65a646e-270b-4286-a328-d40e65d511ab
  spec:
    sourcePod: network-check-source-7cbc45fddc-d4tvc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:58Z"
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42112ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:07:58Z"
    - latency: 2.426692ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 2.588766ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 2.340609ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 2.301387ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 2.109768ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:58Z"
    - latency: 2.512197ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:58Z"
    - latency: 2.327832ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:58Z"
    - latency: 2.545106ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:58Z"
    - latency: 2.650531ms
      message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-221-to-network-check-target-ip-10-0-135-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-221.ec2.internal
      uid: 7b7186da-3f70-4145-b139-836b361f1795
    resourceVersion: "32583"
    uid: 65c640d0-574d-42b8-bd51-44429c3b7964
  spec:
    sourcePod: network-check-source-7cbc45fddc-d4tvc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:58Z"
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.214096ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:07:58Z"
    - latency: 2.280683ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 2.575785ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 2.273756ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 2.282339ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 2.523501ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:58Z"
    - latency: 2.155184ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:01:58Z"
    - latency: 2.254589ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:00:58Z"
    - latency: 2.432897ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:59:58Z"
    - latency: 1.937984ms
      message: 'network-check-target-ip-10-0-135-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T19:58:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-221-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-221.ec2.internal
      uid: 7b7186da-3f70-4145-b139-836b361f1795
    resourceVersion: "32206"
    uid: 10634bae-6ced-423b-8db0-907a356ea25e
  spec:
    sourcePod: network-check-source-7cbc45fddc-d4tvc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:24:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 794.217µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 1.892121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:06:58Z"
    - latency: 1.197734ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 2.415704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:05:58Z"
    - latency: 990.942µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 1.945274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:04:58Z"
    - latency: 978.293µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 1.941582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:03:58Z"
    - latency: 880.567µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:02:58Z"
    - latency: 1.766781ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:02:58Z"
kind: List
metadata:
  resourceVersion: ""