apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T22:25:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-77.us-west-2.compute.internal
      uid: ae0aa2d6-f744-40cc-901d-f175acfef571
    resourceVersion: "113229"
    uid: 65388923-224c-469f-889a-eae9d65329b3
  spec:
    sourcePod: network-check-source-6f78d59f99-4b4vw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T22:32:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.334601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 830.415µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 1.227829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:33:27Z"
    - latency: 904.266µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:32:27Z"
    - latency: 830.769µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:31:27Z"
    - latency: 872.605µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:30:27Z"
    - latency: 1.310095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:29:27Z"
    - latency: 1.503274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:28:27Z"
    - latency: 1.054052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:27:27Z"
    - latency: 901.911µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:26:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T22:25:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-77.us-west-2.compute.internal
      uid: ae0aa2d6-f744-40cc-901d-f175acfef571
    resourceVersion: "114339"
    uid: 8109aaa3-833a-4057-8c58-c84ff3525bd5
  spec:
    sourcePod: network-check-source-6f78d59f99-4b4vw
    targetEndpoint: a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T22:31:27Z"
      message: 'load-balancer-api-external: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 49.328541ms
      message: 'load-balancer-api-external: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:37:27Z"
    - latency: 7.381393ms
      message: 'load-balancer-api-external: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:37:27Z"
    - latency: 48.598548ms
      message: 'load-balancer-api-external: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:36:27Z"
    - latency: 7.609868ms
      message: 'load-balancer-api-external: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:36:27Z"
    - latency: 53.360327ms
      message: 'load-balancer-api-external: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 7.574267ms
      message: 'load-balancer-api-external: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 50.483262ms
      message: 'load-balancer-api-external: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 6.865692ms
      message: 'load-balancer-api-external: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 53.16525ms
      message: 'load-balancer-api-external: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:33:27Z"
    - latency: 9.088765ms
      message: 'load-balancer-api-external: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:33:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T22:25:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-77.us-west-2.compute.internal
      uid: ae0aa2d6-f744-40cc-901d-f175acfef571
    resourceVersion: "114338"
    uid: a5ab534d-d0c4-4e0f-b011-80dd8d9071bd
  spec:
    sourcePod: network-check-source-6f78d59f99-4b4vw
    targetEndpoint: a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T22:31:27Z"
      message: 'load-balancer-api-internal: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 49.316322ms
      message: 'load-balancer-api-internal: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:37:27Z"
    - latency: 7.404371ms
      message: 'load-balancer-api-internal: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:37:27Z"
    - latency: 48.939271ms
      message: 'load-balancer-api-internal: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:36:27Z"
    - latency: 7.658474ms
      message: 'load-balancer-api-internal: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:36:27Z"
    - latency: 50.495781ms
      message: 'load-balancer-api-internal: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 7.601392ms
      message: 'load-balancer-api-internal: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 50.452919ms
      message: 'load-balancer-api-internal: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 6.889955ms
      message: 'load-balancer-api-internal: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 53.151593ms
      message: 'load-balancer-api-internal: tcp connection to a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:33:27Z"
    - latency: 9.122307ms
      message: 'load-balancer-api-internal: resolved host name a40c4aa6d7453489f8ffaf27c6ab6881-5876fe58ba2f5954.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:33:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T22:25:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-77-to-network-check-target-ip-10-0-129-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-77.us-west-2.compute.internal
      uid: ae0aa2d6-f744-40cc-901d-f175acfef571
    resourceVersion: "113226"
    uid: 76fb8025-c273-426d-916a-f7bb5bbe8ec6
  spec:
    sourcePod: network-check-source-6f78d59f99-4b4vw
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T22:32:27Z"
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.003105ms
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 875.778µs
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 1.496337ms
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:33:27Z"
    - latency: 909.513µs
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:32:27Z"
    - latency: 1.401865ms
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:31:27Z"
    - latency: 1.03392ms
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:30:27Z"
    - latency: 902.204µs
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:29:27Z"
    - latency: 826.987µs
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:28:27Z"
    - latency: 949.572µs
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:27:27Z"
    - latency: 881.6µs
      message: 'network-check-target-ip-10-0-129-77: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:26:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T22:25:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-77-to-network-check-target-ip-10-0-130-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-77.us-west-2.compute.internal
      uid: ae0aa2d6-f744-40cc-901d-f175acfef571
    resourceVersion: "113225"
    uid: 66fad766-56fc-43ec-8357-0eee2488df2d
  spec:
    sourcePod: network-check-source-6f78d59f99-4b4vw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T22:32:27Z"
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.028381ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 2.110366ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 2.219396ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:33:27Z"
    - latency: 2.604431ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:32:27Z"
    - latency: 1.97525ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:31:27Z"
    - latency: 2.227338ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:30:27Z"
    - latency: 2.153549ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:29:27Z"
    - latency: 2.730525ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:28:27Z"
    - latency: 1.983505ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:27:27Z"
    - latency: 1.92068ms
      message: 'network-check-target-ip-10-0-130-144: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:26:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T22:25:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-77-to-network-check-target-ip-10-0-138-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-77.us-west-2.compute.internal
      uid: ae0aa2d6-f744-40cc-901d-f175acfef571
    resourceVersion: "113227"
    uid: 61917ca3-7aca-46d6-8665-bbf825cc3a08
  spec:
    sourcePod: network-check-source-6f78d59f99-4b4vw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T22:32:27Z"
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.208763ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 2.51205ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 2.406098ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:33:27Z"
    - latency: 3.120528ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:32:27Z"
    - latency: 2.908362ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:31:27Z"
    - latency: 2.515753ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:30:27Z"
    - latency: 2.611414ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:29:27Z"
    - latency: 2.748247ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:28:27Z"
    - latency: 2.568286ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:27:27Z"
    - latency: 2.208437ms
      message: 'network-check-target-ip-10-0-138-155: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:26:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-01T22:25:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-77.us-west-2.compute.internal
      uid: ae0aa2d6-f744-40cc-901d-f175acfef571
    resourceVersion: "114329"
    uid: aa69b843-7b3e-487e-bce8-786967eb6336
  spec:
    sourcePod: network-check-source-6f78d59f99-4b4vw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-01T22:31:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:37:27Z"
    - latency: 2.053117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:37:27Z"
    - latency: 1.192544ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:36:27Z"
    - latency: 1.932671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:36:27Z"
    - latency: 1.455507ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 1.79599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:35:27Z"
    - latency: 1.144993ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 1.886151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:34:27Z"
    - latency: 994.539µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-01T23:33:27Z"
    - latency: 1.845702ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-01T23:33:27Z"
kind: List
metadata:
  resourceVersion: ""