apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 26a645bd-7234-4b60-86fb-a417593d090d
    resourceVersion: "55416"
    uid: bfee7ca9-4878-4404-b6fc-e56a8128746c
  spec:
    sourcePod: network-check-source-685456655f-w9rl7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:37:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.264631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 1.036517ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 1.108315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:56:09Z"
    - latency: 1.205302ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:55:09Z"
    - latency: 1.371387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:54:09Z"
    - latency: 1.177165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:53:09Z"
    - latency: 1.097409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:52:09Z"
    - latency: 1.477139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:51:09Z"
    - latency: 1.221201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:09Z"
    - latency: 1.052952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 26a645bd-7234-4b60-86fb-a417593d090d
    resourceVersion: "57479"
    uid: 0967eab6-deb4-4a01-915b-53408bbbbf73
  spec:
    sourcePod: network-check-source-685456655f-w9rl7
    targetEndpoint: a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:36:09Z"
      message: 'load-balancer-api-external: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.861901ms
      message: 'load-balancer-api-external: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:00:09Z"
    - latency: 9.225642ms
      message: 'load-balancer-api-external: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:00:09Z"
    - latency: 2.644241ms
      message: 'load-balancer-api-external: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:59:09Z"
    - latency: 11.046693ms
      message: 'load-balancer-api-external: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:59:09Z"
    - latency: 4.738237ms
      message: 'load-balancer-api-external: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 7.29439ms
      message: 'load-balancer-api-external: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 4.590112ms
      message: 'load-balancer-api-external: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 6.894241ms
      message: 'load-balancer-api-external: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 4.427804ms
      message: 'load-balancer-api-external: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:56:09Z"
    - latency: 7.116532ms
      message: 'load-balancer-api-external: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:56:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 26a645bd-7234-4b60-86fb-a417593d090d
    resourceVersion: "57480"
    uid: 37066b4d-9fa6-4449-a6f1-f1230b16b023
  spec:
    sourcePod: network-check-source-685456655f-w9rl7
    targetEndpoint: a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:36:09Z"
      message: 'load-balancer-api-internal: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.325225ms
      message: 'load-balancer-api-internal: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:00:09Z"
    - latency: 9.253322ms
      message: 'load-balancer-api-internal: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:00:09Z"
    - latency: 3.15629ms
      message: 'load-balancer-api-internal: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:59:09Z"
    - latency: 11.076222ms
      message: 'load-balancer-api-internal: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:59:09Z"
    - latency: 4.741098ms
      message: 'load-balancer-api-internal: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 7.349113ms
      message: 'load-balancer-api-internal: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 3.763073ms
      message: 'load-balancer-api-internal: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 6.943856ms
      message: 'load-balancer-api-internal: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 5.419437ms
      message: 'load-balancer-api-internal: tcp connection to a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:56:09Z"
    - latency: 7.149864ms
      message: 'load-balancer-api-internal: resolved host name a3d352029e8fb40c6b34b5dfbc553291-8fa4f765666c441c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:56:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-ip-10-0-130-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 26a645bd-7234-4b60-86fb-a417593d090d
    resourceVersion: "55415"
    uid: 94808b89-a017-4b58-8be0-d5a8cf5b3529
  spec:
    sourcePod: network-check-source-685456655f-w9rl7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:37:09Z"
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.515047ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 2.448215ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 2.976916ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:56:09Z"
    - latency: 2.535397ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:55:09Z"
    - latency: 2.849687ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:54:09Z"
    - latency: 2.273523ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:53:09Z"
    - latency: 2.587972ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:52:09Z"
    - latency: 2.826658ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:51:09Z"
    - latency: 2.885395ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:09Z"
    - latency: 2.564148ms
      message: 'network-check-target-ip-10-0-130-249: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-ip-10-0-135-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 26a645bd-7234-4b60-86fb-a417593d090d
    resourceVersion: "55413"
    uid: 22447a5f-5c8d-4a15-836d-f5bf2404d252
  spec:
    sourcePod: network-check-source-685456655f-w9rl7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:37:09Z"
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.408627ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 1.261105ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 959.437µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:56:09Z"
    - latency: 1.13168ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:55:09Z"
    - latency: 1.023195ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:54:09Z"
    - latency: 1.664398ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:53:09Z"
    - latency: 915.763µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:52:09Z"
    - latency: 1.562542ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:51:09Z"
    - latency: 1.761693ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:09Z"
    - latency: 1.099022ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-ip-10-0-142-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 26a645bd-7234-4b60-86fb-a417593d090d
    resourceVersion: "55414"
    uid: 4bde63e5-4c54-44d4-8e97-d5765615502e
  spec:
    sourcePod: network-check-source-685456655f-w9rl7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:37:09Z"
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.753278ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 2.634092ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 2.602536ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:56:09Z"
    - latency: 2.57984ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:55:09Z"
    - latency: 2.718173ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:54:09Z"
    - latency: 2.662868ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:53:09Z"
    - latency: 2.170567ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:52:09Z"
    - latency: 2.57094ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:51:09Z"
    - latency: 2.438199ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:50:09Z"
    - latency: 2.430423ms
      message: 'network-check-target-ip-10-0-142-68: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:49:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T14:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 26a645bd-7234-4b60-86fb-a417593d090d
    resourceVersion: "57478"
    uid: 51ead5d0-c9db-4b93-b3e8-a1b9a46e73e1
  spec:
    sourcePod: network-check-source-685456655f-w9rl7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T14:36:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.027418ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T15:00:09Z"
    - latency: 2.248934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T15:00:09Z"
    - latency: 1.072695ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:59:09Z"
    - latency: 1.758407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:59:09Z"
    - latency: 947.632µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 1.937162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:58:09Z"
    - latency: 971.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 1.937529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:57:09Z"
    - latency: 990.236µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:56:09Z"
    - latency: 1.83563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:56:09Z"
kind: List
metadata:
  resourceVersion: ""