apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:50:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-35.ec2.internal
      uid: 48c406ea-45b9-42bc-836d-1cd3b019aa8a
    resourceVersion: "19340"
    uid: 0364947a-0296-4562-9b47-e2bae7962c31
  spec:
    sourcePod: network-check-source-7f44b6dd87-fbk5w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:57:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 1.05916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:10:05Z"
    - latency: 969.229µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:09:05Z"
    - latency: 880.999µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:08:05Z"
    - latency: 1.072223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:07:05Z"
    - latency: 1.233838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:06:05Z"
    - latency: 891.728µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:05:05Z"
    - latency: 870.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:04:05Z"
    - latency: 985.49µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:03:05Z"
    - latency: 938.879µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:50:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-35.ec2.internal
      uid: 48c406ea-45b9-42bc-836d-1cd3b019aa8a
    resourceVersion: "20497"
    uid: b62d2e21-a0fd-46f2-a7d5-b3fd20e3241b
  spec:
    sourcePod: network-check-source-7f44b6dd87-fbk5w
    targetEndpoint: ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:56:05Z"
      message: 'load-balancer-api-external: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.428559ms
      message: 'load-balancer-api-external: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:14:05Z"
    - latency: 9.401219ms
      message: 'load-balancer-api-external: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:14:05Z"
    - latency: 5.664779ms
      message: 'load-balancer-api-external: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:13:05Z"
    - latency: 7.265857ms
      message: 'load-balancer-api-external: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:13:05Z"
    - latency: 5.233973ms
      message: 'load-balancer-api-external: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:12:05Z"
    - latency: 9.142785ms
      message: 'load-balancer-api-external: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:12:05Z"
    - latency: 7.243025ms
      message: 'load-balancer-api-external: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 7.610135ms
      message: 'load-balancer-api-external: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 4.417205ms
      message: 'load-balancer-api-external: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:10:05Z"
    - latency: 11.031408ms
      message: 'load-balancer-api-external: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:10:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:50:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-35.ec2.internal
      uid: 48c406ea-45b9-42bc-836d-1cd3b019aa8a
    resourceVersion: "20496"
    uid: 29b91d10-9168-4787-bc3c-21396d9bdccc
  spec:
    sourcePod: network-check-source-7f44b6dd87-fbk5w
    targetEndpoint: ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:56:05Z"
      message: 'load-balancer-api-internal: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.399521ms
      message: 'load-balancer-api-internal: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:14:05Z"
    - latency: 9.377913ms
      message: 'load-balancer-api-internal: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:14:05Z"
    - latency: 5.67772ms
      message: 'load-balancer-api-internal: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:13:05Z"
    - latency: 7.175127ms
      message: 'load-balancer-api-internal: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:13:05Z"
    - latency: 5.204186ms
      message: 'load-balancer-api-internal: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:12:05Z"
    - latency: 9.21931ms
      message: 'load-balancer-api-internal: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:12:05Z"
    - latency: 5.311926ms
      message: 'load-balancer-api-internal: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 7.646807ms
      message: 'load-balancer-api-internal: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 4.451498ms
      message: 'load-balancer-api-internal: tcp connection to ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:10:05Z"
    - latency: 11.109363ms
      message: 'load-balancer-api-internal: resolved host name ac8078a1cc9294b0c8ba399c398dd5f8-357f6578d3972cbb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:10:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:50:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-128-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-35.ec2.internal
      uid: 48c406ea-45b9-42bc-836d-1cd3b019aa8a
    resourceVersion: "19339"
    uid: d864f6ae-1f60-460d-abc7-65b546060750
  spec:
    sourcePod: network-check-source-7f44b6dd87-fbk5w
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:57:05Z"
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.163479ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 2.022752ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:10:05Z"
    - latency: 2.183698ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:09:05Z"
    - latency: 2.107146ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:08:05Z"
    - latency: 2.029972ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:07:05Z"
    - latency: 2.360766ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:06:05Z"
    - latency: 2.262599ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:05:05Z"
    - latency: 2.176962ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:04:05Z"
    - latency: 2.730825ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:03:05Z"
    - latency: 2.05935ms
      message: 'network-check-target-ip-10-0-128-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:50:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-139-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-35.ec2.internal
      uid: 48c406ea-45b9-42bc-836d-1cd3b019aa8a
    resourceVersion: "19338"
    uid: 895c069f-b880-4d1f-ac31-060c25ecbe1a
  spec:
    sourcePod: network-check-source-7f44b6dd87-fbk5w
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:57:05Z"
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.065954ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 2.222504ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:10:05Z"
    - latency: 2.097306ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:09:05Z"
    - latency: 1.922165ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:08:05Z"
    - latency: 2.0027ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:07:05Z"
    - latency: 2.307875ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:06:05Z"
    - latency: 2.122912ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:05:05Z"
    - latency: 2.017885ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:04:05Z"
    - latency: 2.237404ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:03:05Z"
    - latency: 1.809914ms
      message: 'network-check-target-ip-10-0-139-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:50:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-141-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-35.ec2.internal
      uid: 48c406ea-45b9-42bc-836d-1cd3b019aa8a
    resourceVersion: "19337"
    uid: 0b201864-20ac-437a-b588-5227f7e5c36b
  spec:
    sourcePod: network-check-source-7f44b6dd87-fbk5w
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:57:05Z"
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 788.306µs
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 1.054521ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:10:05Z"
    - latency: 796.628µs
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:09:05Z"
    - latency: 681.296µs
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:08:05Z"
    - latency: 835.85µs
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:07:05Z"
    - latency: 1.22272ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:06:05Z"
    - latency: 731.057µs
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:05:05Z"
    - latency: 875.81µs
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:04:05Z"
    - latency: 731.935µs
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:03:05Z"
    - latency: 1.132896ms
      message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:02:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T06:50:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-35.ec2.internal
      uid: 48c406ea-45b9-42bc-836d-1cd3b019aa8a
    resourceVersion: "20495"
    uid: 014eb0b4-73ac-4b43-8c32-03d47fac8715
  spec:
    sourcePod: network-check-source-7f44b6dd87-fbk5w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T06:56:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.306µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:14:05Z"
    - latency: 1.627032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:14:05Z"
    - latency: 870.649µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:13:05Z"
    - latency: 1.705194ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:13:05Z"
    - latency: 883.584µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:12:05Z"
    - latency: 2.108896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:12:05Z"
    - latency: 1.007247ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 1.909225ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:11:05Z"
    - latency: 868.133µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T07:10:05Z"
    - latency: 1.694937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T07:10:05Z"
kind: List
metadata:
  resourceVersion: ""