apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:43:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-121-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-121.ec2.internal
      uid: 4d93dd09-55c7-45fe-9dcf-f7cebb1cdcc3
    resourceVersion: "62449"
    uid: 849ba22e-ad14-40d8-a9f5-f615fd5a77d4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w8r2d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:50:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.790667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 952.051µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 1.29755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 797.562µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 1.088635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:21:18Z"
    - latency: 852.745µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:20:18Z"
    - latency: 1.046941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:19:18Z"
    - latency: 1.589139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:18:18Z"
    - latency: 898.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:17:18Z"
    - latency: 1.055886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:16:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:43:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-121-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-121.ec2.internal
      uid: 4d93dd09-55c7-45fe-9dcf-f7cebb1cdcc3
    resourceVersion: "62450"
    uid: d7f4d637-71f0-492f-9b30-afd1489ca832
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w8r2d
    targetEndpoint: a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:49:18Z"
      message: 'load-balancer-api-external: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.535414ms
      message: 'load-balancer-api-external: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 8.961063ms
      message: 'load-balancer-api-external: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 3.559695ms
      message: 'load-balancer-api-external: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 8.197768ms
      message: 'load-balancer-api-external: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 4.275531ms
      message: 'load-balancer-api-external: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 9.642999ms
      message: 'load-balancer-api-external: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 3.716123ms
      message: 'load-balancer-api-external: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 6.531517ms
      message: 'load-balancer-api-external: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 5.159556ms
      message: 'load-balancer-api-external: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:21:18Z"
    - latency: 6.242744ms
      message: 'load-balancer-api-external: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:21:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:43:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-121-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-121.ec2.internal
      uid: 4d93dd09-55c7-45fe-9dcf-f7cebb1cdcc3
    resourceVersion: "62451"
    uid: 5a94bae4-6764-4860-a109-5e2aab6b8adc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w8r2d
    targetEndpoint: a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:49:18Z"
      message: 'load-balancer-api-internal: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.23548ms
      message: 'load-balancer-api-internal: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 8.908098ms
      message: 'load-balancer-api-internal: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 3.567469ms
      message: 'load-balancer-api-internal: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 8.14439ms
      message: 'load-balancer-api-internal: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 4.289382ms
      message: 'load-balancer-api-internal: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 9.569874ms
      message: 'load-balancer-api-internal: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 3.724188ms
      message: 'load-balancer-api-internal: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 6.627147ms
      message: 'load-balancer-api-internal: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 3.160579ms
      message: 'load-balancer-api-internal: tcp connection to a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:21:18Z"
    - latency: 6.183737ms
      message: 'load-balancer-api-internal: resolved host name a24fe5465df3b44ea9a9562082a6cd25-e53e7cc8b0077d60.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:21:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:43:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-121-to-network-check-target-ip-10-0-128-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-121.ec2.internal
      uid: 4d93dd09-55c7-45fe-9dcf-f7cebb1cdcc3
    resourceVersion: "62447"
    uid: f4e14793-986b-4e98-b57e-a7c32551db18
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w8r2d
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:50:18Z"
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.087694ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 2.211349ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 2.243705ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 1.819374ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 2.574834ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:21:18Z"
    - latency: 2.407902ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:20:18Z"
    - latency: 2.408918ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:19:18Z"
    - latency: 2.685976ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:18:18Z"
    - latency: 2.165397ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:17:18Z"
    - latency: 1.977379ms
      message: 'network-check-target-ip-10-0-128-226: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:16:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:43:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-121-to-network-check-target-ip-10-0-130-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-121.ec2.internal
      uid: 4d93dd09-55c7-45fe-9dcf-f7cebb1cdcc3
    resourceVersion: "62446"
    uid: 9ac9e736-7df4-4978-93cf-c7305efb3b17
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w8r2d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:50:18Z"
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.391446ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 2.281251ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 2.229599ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 2.242937ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 2.23034ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:21:18Z"
    - latency: 2.230229ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:20:18Z"
    - latency: 2.331348ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:19:18Z"
    - latency: 2.413432ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:18:18Z"
    - latency: 2.705491ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:17:18Z"
    - latency: 2.552541ms
      message: 'network-check-target-ip-10-0-130-177: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:16:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:43:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-121-to-network-check-target-ip-10-0-134-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-121.ec2.internal
      uid: 4d93dd09-55c7-45fe-9dcf-f7cebb1cdcc3
    resourceVersion: "62445"
    uid: 70f79390-fae3-4c30-8f3f-13425169d05a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w8r2d
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:50:18Z"
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 839.655µs
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 1.176085ms
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 856.957µs
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 841.374µs
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 1.217796ms
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:21:18Z"
    - latency: 809.244µs
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:20:18Z"
    - latency: 839.948µs
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:19:18Z"
    - latency: 1.480224ms
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:18:18Z"
    - latency: 1.073471ms
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:17:18Z"
    - latency: 842.198µs
      message: 'network-check-target-ip-10-0-134-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:16:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T20:43:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-121-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-121.ec2.internal
      uid: 4d93dd09-55c7-45fe-9dcf-f7cebb1cdcc3
    resourceVersion: "62448"
    uid: 5cddeca7-d587-4fb9-8ffd-610d3fc39d50
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w8r2d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T20:49:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.28965ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 1.825167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:25:18Z"
    - latency: 1.28255ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 1.721909ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:24:18Z"
    - latency: 889.611µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 2.309682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:23:18Z"
    - latency: 792.808µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 1.795125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:22:18Z"
    - latency: 1.294446ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T21:21:18Z"
    - latency: 1.69748ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T21:21:18Z"
kind: List
metadata:
  resourceVersion: ""