apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-132.ec2.internal
      uid: 49f8d4b7-dec2-4cc9-a262-9b3aaf7caa95
    resourceVersion: "50371"
    uid: 7bd998a8-c4b2-48b2-a0be-f5c7c5ea1072
  spec:
    sourcePod: network-check-source-7f44b6dd87-9qkk9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:49:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 721.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:44Z"
    - latency: 1.058485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:44Z"
    - latency: 1.27289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:44Z"
    - latency: 791.571µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:44Z"
    - latency: 1.065715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:13:44Z"
    - latency: 822.747µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 808.649µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 732.649µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 943.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 925.637µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-132.ec2.internal
      uid: 49f8d4b7-dec2-4cc9-a262-9b3aaf7caa95
    resourceVersion: "45087"
    uid: aa758a07-c8d4-406c-a2c5-c32f4c29040e
  spec:
    sourcePod: network-check-source-7f44b6dd87-9qkk9
    targetEndpoint: a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:48:44Z"
      message: 'load-balancer-api-external: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.82763ms
      message: 'load-balancer-api-external: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 7.079ms
      message: 'load-balancer-api-external: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 5.578847ms
      message: 'load-balancer-api-external: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 7.814763ms
      message: 'load-balancer-api-external: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 3.641056ms
      message: 'load-balancer-api-external: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 6.096357ms
      message: 'load-balancer-api-external: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 4.998017ms
      message: 'load-balancer-api-external: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 6.906608ms
      message: 'load-balancer-api-external: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 5.388676ms
      message: 'load-balancer-api-external: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:08:44Z"
    - latency: 6.068956ms
      message: 'load-balancer-api-external: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-132.ec2.internal
      uid: 49f8d4b7-dec2-4cc9-a262-9b3aaf7caa95
    resourceVersion: "45086"
    uid: 836293f9-1ab4-4100-b29c-3d54afc12802
  spec:
    sourcePod: network-check-source-7f44b6dd87-9qkk9
    targetEndpoint: a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:48:44Z"
      message: 'load-balancer-api-internal: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.787168ms
      message: 'load-balancer-api-internal: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 7.142384ms
      message: 'load-balancer-api-internal: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 3.935777ms
      message: 'load-balancer-api-internal: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 7.874165ms
      message: 'load-balancer-api-internal: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 7.264514ms
      message: 'load-balancer-api-internal: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 6.063111ms
      message: 'load-balancer-api-internal: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 5.022009ms
      message: 'load-balancer-api-internal: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 6.869147ms
      message: 'load-balancer-api-internal: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 5.374952ms
      message: 'load-balancer-api-internal: tcp connection to a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:08:44Z"
    - latency: 6.09409ms
      message: 'load-balancer-api-internal: resolved host name a5850cf26c6a1419a883185223e7ef69-35d956afff5acdc4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-132-to-network-check-target-ip-10-0-133-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-132.ec2.internal
      uid: 49f8d4b7-dec2-4cc9-a262-9b3aaf7caa95
    resourceVersion: "50368"
    uid: f0fa61a4-a021-49a5-bd70-24e648c03461
  spec:
    sourcePod: network-check-source-7f44b6dd87-9qkk9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:49:44Z"
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 750.597µs
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:44Z"
    - latency: 1.091995ms
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:44Z"
    - latency: 830.997µs
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:44Z"
    - latency: 851.92µs
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:44Z"
    - latency: 940.209µs
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:13:44Z"
    - latency: 1.010174ms
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 723.939µs
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 1.366454ms
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 903.088µs
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 832.076µs
      message: 'network-check-target-ip-10-0-133-132: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-132-to-network-check-target-ip-10-0-134-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-132.ec2.internal
      uid: 49f8d4b7-dec2-4cc9-a262-9b3aaf7caa95
    resourceVersion: "50369"
    uid: 02673f0e-246a-4b1b-ba96-73d0130d48a0
  spec:
    sourcePod: network-check-source-7f44b6dd87-9qkk9
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:49:44Z"
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.957828ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:44Z"
    - latency: 2.260648ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:44Z"
    - latency: 2.204594ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:44Z"
    - latency: 1.98175ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:44Z"
    - latency: 2.125904ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:13:44Z"
    - latency: 2.15768ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 2.172382ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 2.577386ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 1.925598ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 1.799194ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-132-to-network-check-target-ip-10-0-143-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-132.ec2.internal
      uid: 49f8d4b7-dec2-4cc9-a262-9b3aaf7caa95
    resourceVersion: "50370"
    uid: 4f0c06c2-f163-4b5c-9471-71498b7953af
  spec:
    sourcePod: network-check-source-7f44b6dd87-9qkk9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:49:44Z"
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.381785ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:17:44Z"
    - latency: 1.848701ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:16:44Z"
    - latency: 1.900983ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:15:44Z"
    - latency: 1.955392ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:14:44Z"
    - latency: 2.065396ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:13:44Z"
    - latency: 2.152927ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 2.11602ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 2.096734ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 2.187136ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 1.953281ms
      message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:08:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T16:42:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-132.ec2.internal
      uid: 49f8d4b7-dec2-4cc9-a262-9b3aaf7caa95
    resourceVersion: "45085"
    uid: 7a73519f-8e68-4ead-9853-3b80054b24ff
  spec:
    sourcePod: network-check-source-7f44b6dd87-9qkk9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T16:48:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 833.638µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 1.831774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:12:44Z"
    - latency: 927.863µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 1.837315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:11:44Z"
    - latency: 819.675µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 1.752997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:10:44Z"
    - latency: 1.127318ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 1.611285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:09:44Z"
    - latency: 735.757µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T17:08:44Z"
    - latency: 1.858465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T17:08:44Z"
kind: List
metadata:
  resourceVersion: ""