apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:42:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-194-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-194.ec2.internal
      uid: 9a3a211a-e73b-4fdc-9faa-b3219d163531
    resourceVersion: "68889"
    uid: 4e578f9f-db57-4692-a936-3b57848a8c60
  spec:
    sourcePod: network-check-source-7cbc45fddc-dhhq4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.43341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:45:54Z"
    - latency: 822.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:44:54Z"
    - latency: 1.147598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:43:54Z"
    - latency: 1.474155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 945.299µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 1.607279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 1.119677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 987.293µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:38:54Z"
    - latency: 1.256985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:37:54Z"
    - latency: 1.135903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:36:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:42:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-194-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-194.ec2.internal
      uid: 9a3a211a-e73b-4fdc-9faa-b3219d163531
    resourceVersion: "66554"
    uid: 22b2c64c-9976-462e-b0c8-b3335ebd1d83
  spec:
    sourcePod: network-check-source-7cbc45fddc-dhhq4
    targetEndpoint: aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:48:54Z"
      message: 'load-balancer-api-external: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.440762ms
      message: 'load-balancer-api-external: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 8.062697ms
      message: 'load-balancer-api-external: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 3.73272ms
      message: 'load-balancer-api-external: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 8.447931ms
      message: 'load-balancer-api-external: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 4.277701ms
      message: 'load-balancer-api-external: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 8.342285ms
      message: 'load-balancer-api-external: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 3.452132ms
      message: 'load-balancer-api-external: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 8.082591ms
      message: 'load-balancer-api-external: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 4.919261ms
      message: 'load-balancer-api-external: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:38:54Z"
    - latency: 10.168731ms
      message: 'load-balancer-api-external: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:38:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:42:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-194-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-194.ec2.internal
      uid: 9a3a211a-e73b-4fdc-9faa-b3219d163531
    resourceVersion: "66555"
    uid: 02a91899-2f79-411f-8c18-c1293680f3fd
  spec:
    sourcePod: network-check-source-7cbc45fddc-dhhq4
    targetEndpoint: aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:48:54Z"
      message: 'load-balancer-api-internal: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.465817ms
      message: 'load-balancer-api-internal: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 7.99425ms
      message: 'load-balancer-api-internal: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 3.650347ms
      message: 'load-balancer-api-internal: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 8.378407ms
      message: 'load-balancer-api-internal: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 3.639626ms
      message: 'load-balancer-api-internal: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 8.294ms
      message: 'load-balancer-api-internal: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 3.495036ms
      message: 'load-balancer-api-internal: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 8.165636ms
      message: 'load-balancer-api-internal: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 4.244636ms
      message: 'load-balancer-api-internal: tcp connection to aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:38:54Z"
    - latency: 10.143992ms
      message: 'load-balancer-api-internal: resolved host name aa898e713287f44858dcb597b195464a-472e8302ae4e2b69.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:38:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:42:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-194-to-network-check-target-ip-10-0-129-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-194.ec2.internal
      uid: 9a3a211a-e73b-4fdc-9faa-b3219d163531
    resourceVersion: "68888"
    uid: 5b9cbc82-4694-426e-bb9c-7c7887fbd8c4
  spec:
    sourcePod: network-check-source-7cbc45fddc-dhhq4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:54Z"
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.399673ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:45:54Z"
    - latency: 2.245561ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:44:54Z"
    - latency: 2.280835ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:43:54Z"
    - latency: 2.223705ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 2.476092ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 2.295309ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 2.478322ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 2.473092ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:38:54Z"
    - latency: 2.614691ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:37:54Z"
    - latency: 2.557898ms
      message: 'network-check-target-ip-10-0-129-204: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:36:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:42:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-194-to-network-check-target-ip-10-0-136-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-194.ec2.internal
      uid: 9a3a211a-e73b-4fdc-9faa-b3219d163531
    resourceVersion: "68887"
    uid: cc5a8ed4-6614-4941-94cd-ab0c8aded417
  spec:
    sourcePod: network-check-source-7cbc45fddc-dhhq4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:54Z"
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.37894ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:45:54Z"
    - latency: 1.8582ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:44:54Z"
    - latency: 1.968093ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:43:54Z"
    - latency: 1.822016ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 2.11803ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 2.147659ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 1.995283ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 2.51476ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:38:54Z"
    - latency: 2.109497ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:37:54Z"
    - latency: 2.209533ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:36:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:42:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-194-to-network-check-target-ip-10-0-140-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-194.ec2.internal
      uid: 9a3a211a-e73b-4fdc-9faa-b3219d163531
    resourceVersion: "68886"
    uid: dd997128-440c-4bb5-b52b-0cf36bd0fa7f
  spec:
    sourcePod: network-check-source-7cbc45fddc-dhhq4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:54Z"
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.087216ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:45:54Z"
    - latency: 891.661µs
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:44:54Z"
    - latency: 888.604µs
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:43:54Z"
    - latency: 1.388184ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 993.015µs
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 913.897µs
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 1.397664ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 1.513156ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:38:54Z"
    - latency: 1.016326ms
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:37:54Z"
    - latency: 783.287µs
      message: 'network-check-target-ip-10-0-140-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:36:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:42:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-194-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-194.ec2.internal
      uid: 9a3a211a-e73b-4fdc-9faa-b3219d163531
    resourceVersion: "66553"
    uid: 5a61fb3b-8305-4d92-b49b-4a9af02ffbb1
  spec:
    sourcePod: network-check-source-7cbc45fddc-dhhq4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:48:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.036722ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 1.745348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:42:54Z"
    - latency: 975.601µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 1.914024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:41:54Z"
    - latency: 1.37579ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 1.598787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:40:54Z"
    - latency: 828.522µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 1.902767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:39:54Z"
    - latency: 1.377291ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:38:54Z"
    - latency: 1.805785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:38:54Z"
kind: List
metadata:
  resourceVersion: ""