apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T07:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: a28c7e22-66bc-4db4-ada1-eaf1dc7e0fd9
    resourceVersion: "19983"
    uid: 719a322e-6d68-448f-8b94-f713cb343afc
  spec:
    sourcePod: network-check-source-989f8b8dc-mwb6f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:09:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:25Z"
    - latency: 908.249µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:25Z"
    - latency: 1.121462ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:25Z"
    - latency: 926.183µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:25Z"
    - latency: 1.00371ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:25Z"
    - latency: 1.337231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:25Z"
    - latency: 987.447µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:25Z"
    - latency: 937.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:25Z"
    - latency: 828.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:08:25Z"
    - latency: 936.605µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:07:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T07:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: a28c7e22-66bc-4db4-ada1-eaf1dc7e0fd9
    resourceVersion: "22014"
    uid: 76bda50a-d47b-410e-966a-b812650d9c52
  spec:
    sourcePod: network-check-source-989f8b8dc-mwb6f
    targetEndpoint: aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:08:25Z"
      message: 'load-balancer-api-external: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.251893ms
      message: 'load-balancer-api-external: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:20:25Z"
    - latency: 9.141429ms
      message: 'load-balancer-api-external: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:20:25Z"
    - latency: 3.410104ms
      message: 'load-balancer-api-external: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:19:25Z"
    - latency: 7.315692ms
      message: 'load-balancer-api-external: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:19:25Z"
    - latency: 5.112863ms
      message: 'load-balancer-api-external: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:18:25Z"
    - latency: 8.743123ms
      message: 'load-balancer-api-external: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:18:25Z"
    - latency: 5.293856ms
      message: 'load-balancer-api-external: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:17:25Z"
    - latency: 8.412989ms
      message: 'load-balancer-api-external: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:17:25Z"
    - latency: 3.985469ms
      message: 'load-balancer-api-external: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:25Z"
    - latency: 8.493183ms
      message: 'load-balancer-api-external: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:16:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T07:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: a28c7e22-66bc-4db4-ada1-eaf1dc7e0fd9
    resourceVersion: "22013"
    uid: fe28adf0-2331-4130-b717-66c522ec9dd9
  spec:
    sourcePod: network-check-source-989f8b8dc-mwb6f
    targetEndpoint: aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:08:25Z"
      message: 'load-balancer-api-internal: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.35682ms
      message: 'load-balancer-api-internal: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:20:25Z"
    - latency: 9.17242ms
      message: 'load-balancer-api-internal: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:20:25Z"
    - latency: 5.249927ms
      message: 'load-balancer-api-internal: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:19:25Z"
    - latency: 7.348269ms
      message: 'load-balancer-api-internal: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:19:25Z"
    - latency: 5.083595ms
      message: 'load-balancer-api-internal: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:18:25Z"
    - latency: 8.785044ms
      message: 'load-balancer-api-internal: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:18:25Z"
    - latency: 5.302766ms
      message: 'load-balancer-api-internal: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:17:25Z"
    - latency: 8.349779ms
      message: 'load-balancer-api-internal: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:17:25Z"
    - latency: 4.129273ms
      message: 'load-balancer-api-internal: tcp connection to aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:25Z"
    - latency: 8.556155ms
      message: 'load-balancer-api-internal: resolved host name aa91c20344b7f40738d937b45a7d0665-8a9c699783084b42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:16:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T07:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-ip-10-0-134-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: a28c7e22-66bc-4db4-ada1-eaf1dc7e0fd9
    resourceVersion: "19982"
    uid: 85dc3811-e16d-4ddd-937f-279ad864188c
  spec:
    sourcePod: network-check-source-989f8b8dc-mwb6f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:09:25Z"
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.10819ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:25Z"
    - latency: 2.330658ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:25Z"
    - latency: 2.232795ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:25Z"
    - latency: 2.237703ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:25Z"
    - latency: 2.166078ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:25Z"
    - latency: 2.140383ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:25Z"
    - latency: 2.292727ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:25Z"
    - latency: 2.222662ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:25Z"
    - latency: 2.23406ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:08:25Z"
    - latency: 2.121708ms
      message: 'network-check-target-ip-10-0-134-208: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:07:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T07:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-ip-10-0-135-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: a28c7e22-66bc-4db4-ada1-eaf1dc7e0fd9
    resourceVersion: "19980"
    uid: e3fc800b-3e84-4e18-91c1-a411e5a76ac0
  spec:
    sourcePod: network-check-source-989f8b8dc-mwb6f
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:09:25Z"
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.049µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:25Z"
    - latency: 831.652µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:25Z"
    - latency: 778.747µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:25Z"
    - latency: 843.721µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:25Z"
    - latency: 879.767µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:25Z"
    - latency: 1.300255ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:25Z"
    - latency: 1.182253ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:25Z"
    - latency: 1.072321ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:25Z"
    - latency: 1.391786ms
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:08:25Z"
    - latency: 811.244µs
      message: 'network-check-target-ip-10-0-135-211: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:07:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T07:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-ip-10-0-138-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: a28c7e22-66bc-4db4-ada1-eaf1dc7e0fd9
    resourceVersion: "19981"
    uid: 35f878f1-434d-460f-ba01-0d6f57695030
  spec:
    sourcePod: network-check-source-989f8b8dc-mwb6f
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:09:25Z"
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.426026ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:25Z"
    - latency: 2.315349ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:15:25Z"
    - latency: 2.359196ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:14:25Z"
    - latency: 2.428522ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:13:25Z"
    - latency: 2.475967ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:12:25Z"
    - latency: 2.263305ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:11:25Z"
    - latency: 2.401536ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:10:25Z"
    - latency: 2.476835ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:09:25Z"
    - latency: 2.311552ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:08:25Z"
    - latency: 2.373071ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:07:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T07:02:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-211.ec2.internal
      uid: a28c7e22-66bc-4db4-ada1-eaf1dc7e0fd9
    resourceVersion: "22012"
    uid: fc5d333c-0d61-4301-a906-b53cea7c3441
  spec:
    sourcePod: network-check-source-989f8b8dc-mwb6f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T07:08:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.24µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:20:25Z"
    - latency: 1.623279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:20:25Z"
    - latency: 848.735µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:19:25Z"
    - latency: 1.830188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:19:25Z"
    - latency: 783.272µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:18:25Z"
    - latency: 1.829903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:18:25Z"
    - latency: 757.996µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:17:25Z"
    - latency: 1.772976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:17:25Z"
    - latency: 1.161265ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T07:16:25Z"
    - latency: 1.968156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T07:16:25Z"
kind: List
metadata:
  resourceVersion: ""