apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 07f60115-7f72-4097-9e69-367955af0532
    resourceVersion: "64145"
    uid: 26ba6c88-11c9-494e-9ab6-9c66b0acdeaf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kln74
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:54:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 1.181228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 888.126µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 804.277µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 879.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:25:02Z"
    - latency: 873.163µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:24:02Z"
    - latency: 1.052982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:23:02Z"
    - latency: 834.837µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:22:02Z"
    - latency: 1.16362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:21:02Z"
    - latency: 848.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:20:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 07f60115-7f72-4097-9e69-367955af0532
    resourceVersion: "64147"
    uid: 38cd6bb4-0d06-417e-b7a6-bd1f52d5f416
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kln74
    targetEndpoint: ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:53:02Z"
      message: 'load-balancer-api-external: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.648666ms
      message: 'load-balancer-api-external: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 8.388284ms
      message: 'load-balancer-api-external: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 41.467777ms
      message: 'load-balancer-api-external: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 6.975235ms
      message: 'load-balancer-api-external: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 4.669419ms
      message: 'load-balancer-api-external: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 9.164097ms
      message: 'load-balancer-api-external: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 5.455893ms
      message: 'load-balancer-api-external: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 8.531719ms
      message: 'load-balancer-api-external: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 4.695574ms
      message: 'load-balancer-api-external: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:25:02Z"
    - latency: 7.296916ms
      message: 'load-balancer-api-external: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:25:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 07f60115-7f72-4097-9e69-367955af0532
    resourceVersion: "64146"
    uid: ff125e13-0914-4e14-b207-d0f307435602
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kln74
    targetEndpoint: ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:53:02Z"
      message: 'load-balancer-api-internal: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.310617ms
      message: 'load-balancer-api-internal: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 8.405189ms
      message: 'load-balancer-api-internal: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 5.591558ms
      message: 'load-balancer-api-internal: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 6.987883ms
      message: 'load-balancer-api-internal: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 4.009003ms
      message: 'load-balancer-api-internal: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 9.101427ms
      message: 'load-balancer-api-internal: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 5.444636ms
      message: 'load-balancer-api-internal: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 8.563103ms
      message: 'load-balancer-api-internal: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 4.691542ms
      message: 'load-balancer-api-internal: tcp connection to ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:25:02Z"
    - latency: 7.241941ms
      message: 'load-balancer-api-internal: resolved host name ab863b4c53dba4693b6958dde486a622-c904a354ad6e84aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:25:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-137-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 07f60115-7f72-4097-9e69-367955af0532
    resourceVersion: "64144"
    uid: 3f482af0-e53f-48d9-81a9-b4512949d21d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kln74
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:54:02Z"
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.300104ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 2.299065ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 2.388894ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 2.488715ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 2.085672ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:25:02Z"
    - latency: 1.959692ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:24:02Z"
    - latency: 2.274012ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:23:02Z"
    - latency: 2.440895ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:22:02Z"
    - latency: 2.79212ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:21:02Z"
    - latency: 1.874314ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:20:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-139-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 07f60115-7f72-4097-9e69-367955af0532
    resourceVersion: "64143"
    uid: d14762d7-d46f-4a25-8140-619654a766f2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kln74
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:54:02Z"
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.310665ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 2.354884ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 2.684217ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 2.07132ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 2.111612ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:25:02Z"
    - latency: 2.079444ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:24:02Z"
    - latency: 2.329275ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:23:02Z"
    - latency: 2.393044ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:22:02Z"
    - latency: 2.366626ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:21:02Z"
    - latency: 2.047496ms
      message: 'network-check-target-ip-10-0-139-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:20:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-ip-10-0-143-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 07f60115-7f72-4097-9e69-367955af0532
    resourceVersion: "64141"
    uid: 2798b214-a49b-4b31-a108-6e8d5a14ac69
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kln74
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:54:02Z"
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 744.429µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 847.749µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 1.049689ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 818.804µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 793.6µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:25:02Z"
    - latency: 805.463µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:24:02Z"
    - latency: 1.183737ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:23:02Z"
    - latency: 1.095802ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:22:02Z"
    - latency: 835.695µs
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:21:02Z"
    - latency: 1.012607ms
      message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:20:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-15-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-15.ec2.internal
      uid: 07f60115-7f72-4097-9e69-367955af0532
    resourceVersion: "64142"
    uid: 481b221f-b35c-48dd-86ae-d7e565224249
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kln74
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T18:53:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 806.9µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 1.700281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:29:02Z"
    - latency: 852.826µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 1.558954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:28:02Z"
    - latency: 863.064µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 1.943251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:27:02Z"
    - latency: 834.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 1.642068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:26:02Z"
    - latency: 813.788µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T19:25:02Z"
    - latency: 1.564732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T19:25:02Z"
kind: List
metadata:
  resourceVersion: ""