apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T23:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: d10e400f-a7c0-467e-b41e-b880d41356cb
    resourceVersion: "43414"
    uid: 9b312a4b-18ec-44e1-b3f7-b6f98655a6cf
  spec:
    sourcePod: network-check-source-8894fc9bd-gwhc8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T23:37:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.280586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 942.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 1.192047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:56:29Z"
    - latency: 1.10443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:55:29Z"
    - latency: 1.033654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:54:29Z"
    - latency: 860.579µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:53:29Z"
    - latency: 1.102753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:52:29Z"
    - latency: 1.147773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:51:29Z"
    - latency: 1.174925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:50:29Z"
    - latency: 988.635µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:49:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T23:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: d10e400f-a7c0-467e-b41e-b880d41356cb
    resourceVersion: "45717"
    uid: e64add51-622c-4ad3-befe-73f5ac263d79
  spec:
    sourcePod: network-check-source-8894fc9bd-gwhc8
    targetEndpoint: a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T23:36:29Z"
      message: 'load-balancer-api-external: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.517913ms
      message: 'load-balancer-api-external: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T00:00:29Z"
    - latency: 6.467208ms
      message: 'load-balancer-api-external: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T00:00:29Z"
    - latency: 4.536516ms
      message: 'load-balancer-api-external: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:59:29Z"
    - latency: 6.693426ms
      message: 'load-balancer-api-external: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:59:29Z"
    - latency: 6.82479ms
      message: 'load-balancer-api-external: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 8.597365ms
      message: 'load-balancer-api-external: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 3.861163ms
      message: 'load-balancer-api-external: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 8.615357ms
      message: 'load-balancer-api-external: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 3.795992ms
      message: 'load-balancer-api-external: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:56:29Z"
    - latency: 11.595857ms
      message: 'load-balancer-api-external: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T23:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: d10e400f-a7c0-467e-b41e-b880d41356cb
    resourceVersion: "45716"
    uid: 3a2793c0-83c6-42da-b980-a914f476c5e7
  spec:
    sourcePod: network-check-source-8894fc9bd-gwhc8
    targetEndpoint: a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T23:36:29Z"
      message: 'load-balancer-api-internal: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.529893ms
      message: 'load-balancer-api-internal: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T00:00:29Z"
    - latency: 6.586312ms
      message: 'load-balancer-api-internal: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T00:00:29Z"
    - latency: 4.493132ms
      message: 'load-balancer-api-internal: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:59:29Z"
    - latency: 6.740715ms
      message: 'load-balancer-api-internal: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:59:29Z"
    - latency: 5.439689ms
      message: 'load-balancer-api-internal: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 9.787874ms
      message: 'load-balancer-api-internal: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 5.830775ms
      message: 'load-balancer-api-internal: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 8.70501ms
      message: 'load-balancer-api-internal: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 3.788246ms
      message: 'load-balancer-api-internal: tcp connection to a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:56:29Z"
    - latency: 11.674935ms
      message: 'load-balancer-api-internal: resolved host name a9f32e316f0254825b745c2bf3028a88-c0594cf4c0831e29.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:56:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T23:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-ip-10-0-131-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: d10e400f-a7c0-467e-b41e-b880d41356cb
    resourceVersion: "43411"
    uid: 57631428-ea23-4058-a0bb-a81bc0f52c4e
  spec:
    sourcePod: network-check-source-8894fc9bd-gwhc8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T23:37:29Z"
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.249298ms
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 1.284967ms
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 750.856µs
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:56:29Z"
    - latency: 1.476754ms
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:55:29Z"
    - latency: 1.268887ms
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:54:29Z"
    - latency: 930.47µs
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:53:29Z"
    - latency: 888.72µs
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:52:29Z"
    - latency: 1.252058ms
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:51:29Z"
    - latency: 1.348487ms
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:50:29Z"
    - latency: 1.018943ms
      message: 'network-check-target-ip-10-0-131-43: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:49:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T23:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-ip-10-0-136-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: d10e400f-a7c0-467e-b41e-b880d41356cb
    resourceVersion: "43412"
    uid: a6cb5924-4beb-444e-992a-a7978fe72f9f
  spec:
    sourcePod: network-check-source-8894fc9bd-gwhc8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T23:37:29Z"
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.259305ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 2.564946ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 2.286189ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:56:29Z"
    - latency: 2.155284ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:55:29Z"
    - latency: 2.216682ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:54:29Z"
    - latency: 2.651237ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:53:29Z"
    - latency: 2.0416ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:52:29Z"
    - latency: 2.18524ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:51:29Z"
    - latency: 2.363883ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:50:29Z"
    - latency: 2.490479ms
      message: 'network-check-target-ip-10-0-136-147: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:49:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T23:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-ip-10-0-136-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: d10e400f-a7c0-467e-b41e-b880d41356cb
    resourceVersion: "43413"
    uid: 31703f69-9155-4aba-987c-7445b6bf22a5
  spec:
    sourcePod: network-check-source-8894fc9bd-gwhc8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T23:37:29Z"
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.112488ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 2.086723ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 2.282527ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:56:29Z"
    - latency: 2.078685ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:55:29Z"
    - latency: 2.278128ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:54:29Z"
    - latency: 2.607595ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:53:29Z"
    - latency: 2.055004ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:52:29Z"
    - latency: 1.988371ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:51:29Z"
    - latency: 2.137253ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:50:29Z"
    - latency: 1.992158ms
      message: 'network-check-target-ip-10-0-136-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:49:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T23:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-43.ec2.internal
      uid: d10e400f-a7c0-467e-b41e-b880d41356cb
    resourceVersion: "45715"
    uid: e40b60bb-222d-42ef-a84e-46faec4f4773
  spec:
    sourcePod: network-check-source-8894fc9bd-gwhc8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T23:36:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.000129ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T00:00:29Z"
    - latency: 1.909128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T00:00:29Z"
    - latency: 768.578µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:59:29Z"
    - latency: 1.671611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:59:29Z"
    - latency: 1.160887ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 3.170524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:58:29Z"
    - latency: 839.74µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 2.084267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:57:29Z"
    - latency: 803.106µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T23:56:29Z"
    - latency: 1.693743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T23:56:29Z"
kind: List
metadata:
  resourceVersion: ""