apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T18:39:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 54fae371-1792-4d76-9956-30dd16a79492
    resourceVersion: "53988"
    uid: 7fe4fb46-785e-4081-b425-c8da0042db83
  spec:
    sourcePod: network-check-source-685456655f-54rfc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T18:46:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.213927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 1.472912ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 1.096656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:05:07Z"
    - latency: 1.214706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:04:07Z"
    - latency: 1.356511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:03:07Z"
    - latency: 1.161334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:02:07Z"
    - latency: 1.305441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:01:07Z"
    - latency: 1.389618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:00:07Z"
    - latency: 985.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:59:07Z"
    - latency: 1.352009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:58:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T18:39:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 54fae371-1792-4d76-9956-30dd16a79492
    resourceVersion: "55820"
    uid: c5638398-2987-4387-929b-ff890d6eadc4
  spec:
    sourcePod: network-check-source-685456655f-54rfc
    targetEndpoint: ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T18:45:07Z"
      message: 'load-balancer-api-external: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.99385ms
      message: 'load-balancer-api-external: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:09:07Z"
    - latency: 9.365925ms
      message: 'load-balancer-api-external: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:09:07Z"
    - latency: 5.578667ms
      message: 'load-balancer-api-external: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:08:07Z"
    - latency: 7.625362ms
      message: 'load-balancer-api-external: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:08:07Z"
    - latency: 3.534304ms
      message: 'load-balancer-api-external: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 8.062585ms
      message: 'load-balancer-api-external: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 4.786092ms
      message: 'load-balancer-api-external: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 6.591041ms
      message: 'load-balancer-api-external: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 5.193861ms
      message: 'load-balancer-api-external: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:05:07Z"
    - latency: 7.146472ms
      message: 'load-balancer-api-external: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:05:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T18:39:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 54fae371-1792-4d76-9956-30dd16a79492
    resourceVersion: "55819"
    uid: de90fb6a-0b47-4b8a-8b6a-56ff1ca87282
  spec:
    sourcePod: network-check-source-685456655f-54rfc
    targetEndpoint: ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T18:45:07Z"
      message: 'load-balancer-api-internal: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.029375ms
      message: 'load-balancer-api-internal: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:09:07Z"
    - latency: 9.32548ms
      message: 'load-balancer-api-internal: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:09:07Z"
    - latency: 5.582288ms
      message: 'load-balancer-api-internal: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:08:07Z"
    - latency: 7.596306ms
      message: 'load-balancer-api-internal: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:08:07Z"
    - latency: 3.548547ms
      message: 'load-balancer-api-internal: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 8.006403ms
      message: 'load-balancer-api-internal: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 4.82086ms
      message: 'load-balancer-api-internal: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 6.507901ms
      message: 'load-balancer-api-internal: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 5.17761ms
      message: 'load-balancer-api-internal: tcp connection to ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:05:07Z"
    - latency: 7.082387ms
      message: 'load-balancer-api-internal: resolved host name ad72ab57207f9481fbc99a6f5d71f682-31a91b3fc9861468.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:05:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T18:39:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-ip-10-0-134-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 54fae371-1792-4d76-9956-30dd16a79492
    resourceVersion: "53985"
    uid: 857aef92-a937-4f1c-90e6-6034edf32d6a
  spec:
    sourcePod: network-check-source-685456655f-54rfc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T18:46:07Z"
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.342µs
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 1.234215ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 994.953µs
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:05:07Z"
    - latency: 1.430586ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:04:07Z"
    - latency: 1.139184ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:03:07Z"
    - latency: 1.125583ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:02:07Z"
    - latency: 1.748392ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:01:07Z"
    - latency: 1.383627ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:00:07Z"
    - latency: 1.113188ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:59:07Z"
    - latency: 1.152414ms
      message: 'network-check-target-ip-10-0-134-63: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:58:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T18:39:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-ip-10-0-135-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 54fae371-1792-4d76-9956-30dd16a79492
    resourceVersion: "53987"
    uid: f517b013-2da9-41ac-979e-508fcf4883b3
  spec:
    sourcePod: network-check-source-685456655f-54rfc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T18:46:07Z"
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.796895ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 2.322668ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 2.263829ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:05:07Z"
    - latency: 2.662794ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:04:07Z"
    - latency: 2.4727ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:03:07Z"
    - latency: 2.512683ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:02:07Z"
    - latency: 2.642066ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:01:07Z"
    - latency: 2.5374ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:00:07Z"
    - latency: 2.601229ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:59:07Z"
    - latency: 2.488975ms
      message: 'network-check-target-ip-10-0-135-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:58:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T18:39:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-ip-10-0-135-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 54fae371-1792-4d76-9956-30dd16a79492
    resourceVersion: "53986"
    uid: 5a250a01-2eec-436b-99b0-6994dc404748
  spec:
    sourcePod: network-check-source-685456655f-54rfc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T18:46:07Z"
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.585447ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 2.45999ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 3.029029ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:05:07Z"
    - latency: 2.536422ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:04:07Z"
    - latency: 2.837125ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:03:07Z"
    - latency: 3.18137ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:02:07Z"
    - latency: 2.703405ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:01:07Z"
    - latency: 2.659732ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:00:07Z"
    - latency: 2.399548ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:59:07Z"
    - latency: 2.540967ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T18:58:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T18:39:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-63.ec2.internal
      uid: 54fae371-1792-4d76-9956-30dd16a79492
    resourceVersion: "55818"
    uid: f323a721-3f18-469b-98e3-b6f832528ded
  spec:
    sourcePod: network-check-source-685456655f-54rfc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T18:45:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.754µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:09:07Z"
    - latency: 1.843306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:09:07Z"
    - latency: 944.432µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:08:07Z"
    - latency: 2.254807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:08:07Z"
    - latency: 978.24µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 1.953405ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:07:07Z"
    - latency: 1.114177ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 2.066779ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:06:07Z"
    - latency: 1.243304ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T19:05:07Z"
    - latency: 1.897411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T19:05:07Z"
kind: List
metadata:
  resourceVersion: ""