apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T15:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-111.ec2.internal
      uid: 9037a410-d79a-46d8-aefd-a74e0cee0691
    resourceVersion: "88547"
    uid: 4e3e1ea3-4ff5-45b0-9910-790e9d12d8c0
  spec:
    sourcePod: network-check-source-6f8b768455-7tvxm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:02:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.160486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 1.273443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 1.09451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:53Z"
    - latency: 1.054965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:53Z"
    - latency: 1.527345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:01:53Z"
    - latency: 1.28386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:00:53Z"
    - latency: 1.051978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:59:53Z"
    - latency: 1.212809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:58:53Z"
    - latency: 1.102455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:57:53Z"
    - latency: 923.911µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:56:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T15:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-111.ec2.internal
      uid: 9037a410-d79a-46d8-aefd-a74e0cee0691
    resourceVersion: "90492"
    uid: b19167fb-885c-4fea-84da-0f1317456d77
  spec:
    sourcePod: network-check-source-6f8b768455-7tvxm
    targetEndpoint: a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:01:53Z"
      message: 'load-balancer-api-external: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.682092ms
      message: 'load-balancer-api-external: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:07:53Z"
    - latency: 7.107664ms
      message: 'load-balancer-api-external: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:07:53Z"
    - latency: 4.81845ms
      message: 'load-balancer-api-external: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:06:53Z"
    - latency: 7.488689ms
      message: 'load-balancer-api-external: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:06:53Z"
    - latency: 5.703937ms
      message: 'load-balancer-api-external: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 7.942587ms
      message: 'load-balancer-api-external: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 5.419706ms
      message: 'load-balancer-api-external: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 7.988994ms
      message: 'load-balancer-api-external: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 5.528435ms
      message: 'load-balancer-api-external: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:53Z"
    - latency: 7.435114ms
      message: 'load-balancer-api-external: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:03:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T15:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-111.ec2.internal
      uid: 9037a410-d79a-46d8-aefd-a74e0cee0691
    resourceVersion: "90493"
    uid: 44e78789-89d6-4807-bafd-9fdaed0f9458
  spec:
    sourcePod: network-check-source-6f8b768455-7tvxm
    targetEndpoint: a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:01:53Z"
      message: 'load-balancer-api-internal: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.784001ms
      message: 'load-balancer-api-internal: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:07:53Z"
    - latency: 7.187487ms
      message: 'load-balancer-api-internal: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:07:53Z"
    - latency: 6.073919ms
      message: 'load-balancer-api-internal: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:06:53Z"
    - latency: 7.57788ms
      message: 'load-balancer-api-internal: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:06:53Z"
    - latency: 6.291457ms
      message: 'load-balancer-api-internal: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 7.994459ms
      message: 'load-balancer-api-internal: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 5.392573ms
      message: 'load-balancer-api-internal: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 8.150508ms
      message: 'load-balancer-api-internal: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 4.569746ms
      message: 'load-balancer-api-internal: tcp connection to a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:53Z"
    - latency: 7.407056ms
      message: 'load-balancer-api-internal: resolved host name a4ca9a476c8dc4403bc25a4a438ea6b6-891ec41858913861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:03:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T15:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-111-to-network-check-target-ip-10-0-136-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-111.ec2.internal
      uid: 9037a410-d79a-46d8-aefd-a74e0cee0691
    resourceVersion: "88546"
    uid: e781442e-4d0e-4e27-be12-af46887483db
  spec:
    sourcePod: network-check-source-6f8b768455-7tvxm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:02:53Z"
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.687297ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 2.563868ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 2.453484ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:53Z"
    - latency: 2.462995ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:53Z"
    - latency: 2.58524ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:01:53Z"
    - latency: 2.31582ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:00:53Z"
    - latency: 2.695615ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:59:53Z"
    - latency: 2.268795ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:58:53Z"
    - latency: 2.278319ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:57:53Z"
    - latency: 2.240919ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:56:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T15:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-111-to-network-check-target-ip-10-0-137-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-111.ec2.internal
      uid: 9037a410-d79a-46d8-aefd-a74e0cee0691
    resourceVersion: "88544"
    uid: 56711cd3-75d9-4fdd-9e86-1d8d8bd3032b
  spec:
    sourcePod: network-check-source-6f8b768455-7tvxm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:02:53Z"
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.192543ms
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 976.354µs
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 1.554496ms
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:53Z"
    - latency: 1.077236ms
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:53Z"
    - latency: 1.692613ms
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:01:53Z"
    - latency: 1.031202ms
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:00:53Z"
    - latency: 1.428403ms
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:59:53Z"
    - latency: 1.236751ms
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:58:53Z"
    - latency: 964.437µs
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:57:53Z"
    - latency: 909.243µs
      message: 'network-check-target-ip-10-0-137-111: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:56:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T15:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-111-to-network-check-target-ip-10-0-143-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-111.ec2.internal
      uid: 9037a410-d79a-46d8-aefd-a74e0cee0691
    resourceVersion: "88545"
    uid: 60e265cb-12a4-4a32-8252-d5ceed0668fa
  spec:
    sourcePod: network-check-source-6f8b768455-7tvxm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:02:53Z"
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.155042ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 2.309582ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 2.481217ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:53Z"
    - latency: 2.31764ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:02:53Z"
    - latency: 2.871198ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:01:53Z"
    - latency: 2.333178ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:00:53Z"
    - latency: 2.184895ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:59:53Z"
    - latency: 2.475272ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:58:53Z"
    - latency: 2.411635ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:57:53Z"
    - latency: 1.969837ms
      message: 'network-check-target-ip-10-0-143-143: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T16:56:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T15:55:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-111.ec2.internal
      uid: 9037a410-d79a-46d8-aefd-a74e0cee0691
    resourceVersion: "90487"
    uid: 981a6876-484f-474e-ae82-b80d0eb05464
  spec:
    sourcePod: network-check-source-6f8b768455-7tvxm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T16:01:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.859µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:07:53Z"
    - latency: 2.383795ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:07:53Z"
    - latency: 894.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:06:53Z"
    - latency: 2.208092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:06:53Z"
    - latency: 1.390904ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 2.109765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:05:53Z"
    - latency: 1.231602ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 2.229134ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:04:53Z"
    - latency: 1.04186ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T17:03:53Z"
    - latency: 1.789876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T17:03:53Z"
kind: List
metadata:
  resourceVersion: ""