apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 106588f4-74b6-424b-85c4-8e5ae8bd9da0
    resourceVersion: "21862"
    uid: 4c756cdd-b527-4390-a17b-a67e970609fe
  spec:
    sourcePod: network-check-source-989f8b8dc-vcqc5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:26Z"
    - latency: 838.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:26Z"
    - latency: 948.524µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:26Z"
    - latency: 948.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 862.097µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 1.1843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 1.031846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 1.588962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:26Z"
    - latency: 1.273823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:26Z"
    - latency: 1.005323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 106588f4-74b6-424b-85c4-8e5ae8bd9da0
    resourceVersion: "20451"
    uid: 8d9ad86a-10f1-42cb-84be-458aa9d36464
  spec:
    sourcePod: network-check-source-989f8b8dc-vcqc5
    targetEndpoint: abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:50:26Z"
      message: 'load-balancer-api-external: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.06659ms
      message: 'load-balancer-api-external: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 7.066773ms
      message: 'load-balancer-api-external: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 6.030677ms
      message: 'load-balancer-api-external: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 11.499317ms
      message: 'load-balancer-api-external: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 6.321373ms
      message: 'load-balancer-api-external: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 8.541856ms
      message: 'load-balancer-api-external: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 6.244788ms
      message: 'load-balancer-api-external: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 7.092792ms
      message: 'load-balancer-api-external: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 5.303461ms
      message: 'load-balancer-api-external: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:26Z"
    - latency: 8.399014ms
      message: 'load-balancer-api-external: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:58:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 106588f4-74b6-424b-85c4-8e5ae8bd9da0
    resourceVersion: "20450"
    uid: 241c6959-0afa-43f9-88ce-5e8df62f2848
  spec:
    sourcePod: network-check-source-989f8b8dc-vcqc5
    targetEndpoint: abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:50:26Z"
      message: 'load-balancer-api-internal: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.032246ms
      message: 'load-balancer-api-internal: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 7.138927ms
      message: 'load-balancer-api-internal: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 4.550932ms
      message: 'load-balancer-api-internal: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 11.452921ms
      message: 'load-balancer-api-internal: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 6.305939ms
      message: 'load-balancer-api-internal: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 8.499624ms
      message: 'load-balancer-api-internal: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 3.697651ms
      message: 'load-balancer-api-internal: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 7.181714ms
      message: 'load-balancer-api-internal: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 5.292592ms
      message: 'load-balancer-api-internal: tcp connection to abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:26Z"
    - latency: 8.465739ms
      message: 'load-balancer-api-internal: resolved host name abf30059267714ce593b4997809d0d10-cbe7ec55d4ce644d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:58:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-ip-10-0-134-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 106588f4-74b6-424b-85c4-8e5ae8bd9da0
    resourceVersion: "21861"
    uid: 2fea800d-01f9-4d7d-9b67-64ff4867d3b1
  spec:
    sourcePod: network-check-source-989f8b8dc-vcqc5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:26Z"
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.308947ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:26Z"
    - latency: 2.140076ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:26Z"
    - latency: 2.263096ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:26Z"
    - latency: 2.027204ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 2.148351ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 2.022598ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 1.928357ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 2.294256ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:26Z"
    - latency: 2.195273ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:26Z"
    - latency: 2.441102ms
      message: 'network-check-target-ip-10-0-134-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-ip-10-0-136-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 106588f4-74b6-424b-85c4-8e5ae8bd9da0
    resourceVersion: "21859"
    uid: cf2915e5-437b-4e05-b680-52d6908d59b0
  spec:
    sourcePod: network-check-source-989f8b8dc-vcqc5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:26Z"
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.301µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:26Z"
    - latency: 811.536µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:26Z"
    - latency: 1.59283ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:26Z"
    - latency: 1.162877ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 1.435954ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 845.319µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 1.302071ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 781.537µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:26Z"
    - latency: 861.845µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:26Z"
    - latency: 1.302955ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-ip-10-0-138-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 106588f4-74b6-424b-85c4-8e5ae8bd9da0
    resourceVersion: "21860"
    uid: 517e0bad-7d33-4a61-8e9f-e09fb0fcee48
  spec:
    sourcePod: network-check-source-989f8b8dc-vcqc5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:26Z"
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.058216ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:26Z"
    - latency: 1.633789ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:26Z"
    - latency: 1.860161ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:26Z"
    - latency: 1.976985ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 2.013645ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 2.055654ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 1.978215ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 1.782941ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:26Z"
    - latency: 2.20018ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:26Z"
    - latency: 2.004024ms
      message: 'network-check-target-ip-10-0-138-183: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 106588f4-74b6-424b-85c4-8e5ae8bd9da0
    resourceVersion: "20449"
    uid: b98d25ce-1ac2-4bb7-ab3f-3073547068c2
  spec:
    sourcePod: network-check-source-989f8b8dc-vcqc5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:50:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030949ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 1.863492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:02:26Z"
    - latency: 1.045808ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 1.596009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:01:26Z"
    - latency: 973.026µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 1.704935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:00:26Z"
    - latency: 1.077965ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 1.723396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:59:26Z"
    - latency: 1.004629ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:26Z"
    - latency: 1.729683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:58:26Z"
kind: List
metadata:
  resourceVersion: ""