apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 45b56ef2-a740-444f-9554-84dda6cc561a
    resourceVersion: "38629"
    uid: ccfe6106-dcae-4e1b-bc94-0ed66fd347af
  spec:
    sourcePod: network-check-source-6f8b768455-fd27s
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.888µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:31:17Z"
    - latency: 1.078032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 966.532µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 906.11µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 1.181075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 1.094272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:26:17Z"
    - latency: 1.158079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:25:17Z"
    - latency: 990.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:24:17Z"
    - latency: 761.106µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:23:17Z"
    - latency: 1.101099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 45b56ef2-a740-444f-9554-84dda6cc561a
    resourceVersion: "38105"
    uid: 5ccd8274-c0f8-4fb3-9253-e6dbf480e6b6
  spec:
    sourcePod: network-check-source-6f8b768455-fd27s
    targetEndpoint: a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:48:17Z"
      message: 'load-balancer-api-external: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.816728ms
      message: 'load-balancer-api-external: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 7.774751ms
      message: 'load-balancer-api-external: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 4.736724ms
      message: 'load-balancer-api-external: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 8.281523ms
      message: 'load-balancer-api-external: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 4.350696ms
      message: 'load-balancer-api-external: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 8.430524ms
      message: 'load-balancer-api-external: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 4.405652ms
      message: 'load-balancer-api-external: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 8.031062ms
      message: 'load-balancer-api-external: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 4.448177ms
      message: 'load-balancer-api-external: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:26:17Z"
    - latency: 8.158457ms
      message: 'load-balancer-api-external: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:26:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 45b56ef2-a740-444f-9554-84dda6cc561a
    resourceVersion: "38106"
    uid: 1f46c458-7f2c-40a1-8ce1-717483c6a083
  spec:
    sourcePod: network-check-source-6f8b768455-fd27s
    targetEndpoint: a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:48:17Z"
      message: 'load-balancer-api-internal: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.435883ms
      message: 'load-balancer-api-internal: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 7.806103ms
      message: 'load-balancer-api-internal: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 4.775237ms
      message: 'load-balancer-api-internal: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 8.343404ms
      message: 'load-balancer-api-internal: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 3.793776ms
      message: 'load-balancer-api-internal: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 8.441756ms
      message: 'load-balancer-api-internal: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 7.198643ms
      message: 'load-balancer-api-internal: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 8.008909ms
      message: 'load-balancer-api-internal: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 4.256184ms
      message: 'load-balancer-api-internal: tcp connection to a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:26:17Z"
    - latency: 8.035943ms
      message: 'load-balancer-api-internal: resolved host name a48006961967e42bd95cda6363912e52-c689d2ad153c8b45.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:26:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-ip-10-0-128-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 45b56ef2-a740-444f-9554-84dda6cc561a
    resourceVersion: "38628"
    uid: 7b451e55-3029-4035-96b2-738354fb21f4
  spec:
    sourcePod: network-check-source-6f8b768455-fd27s
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:17Z"
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.461µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:31:17Z"
    - latency: 879.048µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 958.477µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 1.256182ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 809.831µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 920.749µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:26:17Z"
    - latency: 1.479604ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:25:17Z"
    - latency: 1.304441ms
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:24:17Z"
    - latency: 892.438µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:23:17Z"
    - latency: 876.656µs
      message: 'network-check-target-ip-10-0-128-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-ip-10-0-140-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 45b56ef2-a740-444f-9554-84dda6cc561a
    resourceVersion: "38626"
    uid: 1d8c3108-ad94-458d-8b53-9893c39a1e34
  spec:
    sourcePod: network-check-source-6f8b768455-fd27s
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:17Z"
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.975454ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:31:17Z"
    - latency: 1.730764ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 1.806208ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 2.176948ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 1.818447ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 1.809779ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:26:17Z"
    - latency: 1.864946ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:25:17Z"
    - latency: 1.997883ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:24:17Z"
    - latency: 1.889515ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:23:17Z"
    - latency: 1.916339ms
      message: 'network-check-target-ip-10-0-140-157: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-ip-10-0-143-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 45b56ef2-a740-444f-9554-84dda6cc561a
    resourceVersion: "38627"
    uid: 943b76ab-3e04-4ce6-8b69-23a695af9a46
  spec:
    sourcePod: network-check-source-6f8b768455-fd27s
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:49:17Z"
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.343504ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:31:17Z"
    - latency: 2.387493ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 2.222216ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 2.090166ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 2.234279ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 2.357563ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:26:17Z"
    - latency: 2.262291ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:25:17Z"
    - latency: 2.336206ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:24:17Z"
    - latency: 2.067236ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:23:17Z"
    - latency: 2.390571ms
      message: 'network-check-target-ip-10-0-143-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:42:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-144.ec2.internal
      uid: 45b56ef2-a740-444f-9554-84dda6cc561a
    resourceVersion: "38103"
    uid: c5456097-38ce-4af0-a93f-f3a2a99f2e54
  spec:
    sourcePod: network-check-source-6f8b768455-fd27s
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:48:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.217951ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 1.78261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:30:17Z"
    - latency: 742.714µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 1.765449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:29:17Z"
    - latency: 830.66µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 1.910079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:28:17Z"
    - latency: 839.812µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 1.656044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:27:17Z"
    - latency: 1.061598ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:26:17Z"
    - latency: 1.830568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:26:17Z"
kind: List
metadata:
  resourceVersion: ""