apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:44:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-247-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-247.ec2.internal
      uid: 0a1bba49-d939-407c-877d-fedff3834ecb
    resourceVersion: "46703"
    uid: 9696d0e0-9a7b-4fb3-945f-7617bf75f324
  spec:
    sourcePod: network-check-source-dbd9cf844-vrclj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:51:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.513µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 1.218049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 2.137036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:10:44Z"
    - latency: 1.160292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:09:44Z"
    - latency: 1.291875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:08:44Z"
    - latency: 1.187552ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:44Z"
    - latency: 1.195788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:44Z"
    - latency: 1.019285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:44Z"
    - latency: 967.199µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:44Z"
    - latency: 1.132891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:44:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-247-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-247.ec2.internal
      uid: 0a1bba49-d939-407c-877d-fedff3834ecb
    resourceVersion: "48870"
    uid: 9146b842-c3fc-4504-8f9d-227bad3032f7
  spec:
    sourcePod: network-check-source-dbd9cf844-vrclj
    targetEndpoint: aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:50:44Z"
      message: 'load-balancer-api-external: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.688373ms
      message: 'load-balancer-api-external: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:14:44Z"
    - latency: 7.555038ms
      message: 'load-balancer-api-external: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:14:44Z"
    - latency: 4.007106ms
      message: 'load-balancer-api-external: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:13:44Z"
    - latency: 7.437294ms
      message: 'load-balancer-api-external: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:13:44Z"
    - latency: 6.218533ms
      message: 'load-balancer-api-external: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 12.429163ms
      message: 'load-balancer-api-external: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 5.618705ms
      message: 'load-balancer-api-external: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 7.536397ms
      message: 'load-balancer-api-external: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 5.90728ms
      message: 'load-balancer-api-external: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:10:44Z"
    - latency: 7.716586ms
      message: 'load-balancer-api-external: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:10:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:44:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-247-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-247.ec2.internal
      uid: 0a1bba49-d939-407c-877d-fedff3834ecb
    resourceVersion: "48869"
    uid: 628835a4-aa30-4c93-802a-bfc7d690bd05
  spec:
    sourcePod: network-check-source-dbd9cf844-vrclj
    targetEndpoint: aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:50:44Z"
      message: 'load-balancer-api-internal: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.640242ms
      message: 'load-balancer-api-internal: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:14:44Z"
    - latency: 7.615905ms
      message: 'load-balancer-api-internal: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:14:44Z"
    - latency: 5.752991ms
      message: 'load-balancer-api-internal: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:13:44Z"
    - latency: 7.24002ms
      message: 'load-balancer-api-internal: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:13:44Z"
    - latency: 4.83143ms
      message: 'load-balancer-api-internal: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 12.311378ms
      message: 'load-balancer-api-internal: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 5.607158ms
      message: 'load-balancer-api-internal: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 7.600332ms
      message: 'load-balancer-api-internal: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 5.895897ms
      message: 'load-balancer-api-internal: tcp connection to aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:10:44Z"
    - latency: 7.746963ms
      message: 'load-balancer-api-internal: resolved host name aa3447e98278d4cc4a6f93519723cb94-90085ce606ec7889.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:10:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:44:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-247-to-network-check-target-ip-10-0-129-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-247.ec2.internal
      uid: 0a1bba49-d939-407c-877d-fedff3834ecb
    resourceVersion: "46702"
    uid: 1fffee4d-33ab-47c0-a216-9902ad7b31c0
  spec:
    sourcePod: network-check-source-dbd9cf844-vrclj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:51:44Z"
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.794777ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 2.409958ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 2.432978ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:10:44Z"
    - latency: 2.135069ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:09:44Z"
    - latency: 2.544227ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:08:44Z"
    - latency: 2.41223ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:44Z"
    - latency: 2.275946ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:44Z"
    - latency: 2.425997ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:44Z"
    - latency: 2.448405ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:44Z"
    - latency: 2.559491ms
      message: 'network-check-target-ip-10-0-129-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:44:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-247-to-network-check-target-ip-10-0-140-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-247.ec2.internal
      uid: 0a1bba49-d939-407c-877d-fedff3834ecb
    resourceVersion: "46700"
    uid: 64e616a4-2257-4eda-b8ca-f995a6a49cda
  spec:
    sourcePod: network-check-source-dbd9cf844-vrclj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:51:44Z"
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.346532ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 1.023629ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 1.124504ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:10:44Z"
    - latency: 971.328µs
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:09:44Z"
    - latency: 1.839478ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:08:44Z"
    - latency: 1.015286ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:44Z"
    - latency: 1.025144ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:44Z"
    - latency: 975.183µs
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:44Z"
    - latency: 1.665204ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:44Z"
    - latency: 990.599µs
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:44:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-247-to-network-check-target-ip-10-0-141-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-247.ec2.internal
      uid: 0a1bba49-d939-407c-877d-fedff3834ecb
    resourceVersion: "46701"
    uid: 9786a397-1073-4029-97da-fb2e47c0cd04
  spec:
    sourcePod: network-check-source-dbd9cf844-vrclj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:51:44Z"
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.399489ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 2.185428ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 2.502179ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:10:44Z"
    - latency: 2.410554ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:09:44Z"
    - latency: 2.628295ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:08:44Z"
    - latency: 2.378056ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:07:44Z"
    - latency: 2.492416ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:06:44Z"
    - latency: 2.515518ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:05:44Z"
    - latency: 2.775367ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:04:44Z"
    - latency: 2.470116ms
      message: 'network-check-target-ip-10-0-141-248: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:03:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T19:44:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-247-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-247.ec2.internal
      uid: 0a1bba49-d939-407c-877d-fedff3834ecb
    resourceVersion: "48868"
    uid: e295f960-9718-4060-8d3c-9bb219cc5eec
  spec:
    sourcePod: network-check-source-dbd9cf844-vrclj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T19:50:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.495µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:14:44Z"
    - latency: 1.982841ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:14:44Z"
    - latency: 1.285845ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:13:44Z"
    - latency: 2.162706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:13:44Z"
    - latency: 974.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 1.828677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:12:44Z"
    - latency: 944.462µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 2.193261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:11:44Z"
    - latency: 933.25µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T20:10:44Z"
    - latency: 2.47084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T20:10:44Z"
kind: List
metadata:
  resourceVersion: ""