apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-126-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-126.ec2.internal
      uid: df882fdf-af6c-4bb6-86cf-b055e46a8830
    resourceVersion: "21976"
    uid: 16203b58-728b-4ea8-896c-9f8bdc28a6db
  spec:
    sourcePod: network-check-source-6f8b768455-jsp45
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T12:01:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.389381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:22:46Z"
    - latency: 1.739998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:21:46Z"
    - latency: 902.49µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:20:46Z"
    - latency: 1.158122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:19:46Z"
    - latency: 1.222256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 958.994µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 1.201122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 1.262889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 848.788µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:14:46Z"
    - latency: 1.210441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-126-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-126.ec2.internal
      uid: df882fdf-af6c-4bb6-86cf-b055e46a8830
    resourceVersion: "20414"
    uid: ccb291fe-42db-45ce-bf87-2550a42b46db
  spec:
    sourcePod: network-check-source-6f8b768455-jsp45
    targetEndpoint: ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T12:00:46Z"
      message: 'load-balancer-api-external: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.471105ms
      message: 'load-balancer-api-external: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 8.573903ms
      message: 'load-balancer-api-external: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 4.490725ms
      message: 'load-balancer-api-external: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 8.706677ms
      message: 'load-balancer-api-external: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 5.161036ms
      message: 'load-balancer-api-external: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 7.53113ms
      message: 'load-balancer-api-external: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 4.492797ms
      message: 'load-balancer-api-external: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 9.009723ms
      message: 'load-balancer-api-external: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 4.810702ms
      message: 'load-balancer-api-external: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:14:46Z"
    - latency: 8.220184ms
      message: 'load-balancer-api-external: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:14:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-126-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-126.ec2.internal
      uid: df882fdf-af6c-4bb6-86cf-b055e46a8830
    resourceVersion: "20415"
    uid: b6d03494-daef-4da7-a9c6-41127b90a4cc
  spec:
    sourcePod: network-check-source-6f8b768455-jsp45
    targetEndpoint: ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T12:00:46Z"
      message: 'load-balancer-api-internal: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.490021ms
      message: 'load-balancer-api-internal: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 8.591522ms
      message: 'load-balancer-api-internal: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 3.702218ms
      message: 'load-balancer-api-internal: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 8.689866ms
      message: 'load-balancer-api-internal: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 5.183569ms
      message: 'load-balancer-api-internal: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 7.51609ms
      message: 'load-balancer-api-internal: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 5.705473ms
      message: 'load-balancer-api-internal: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 9.063688ms
      message: 'load-balancer-api-internal: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 4.804218ms
      message: 'load-balancer-api-internal: tcp connection to ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:14:46Z"
    - latency: 8.243369ms
      message: 'load-balancer-api-internal: resolved host name ab20a9663df324725bff617a5af4401f-d2f37198beafa664.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:14:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-126-to-network-check-target-ip-10-0-134-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-126.ec2.internal
      uid: df882fdf-af6c-4bb6-86cf-b055e46a8830
    resourceVersion: "21975"
    uid: 08248b98-a951-4b41-a6f4-91a10f470151
  spec:
    sourcePod: network-check-source-6f8b768455-jsp45
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T12:01:46Z"
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.4173ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:22:46Z"
    - latency: 2.493772ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:21:46Z"
    - latency: 2.155576ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:20:46Z"
    - latency: 2.314611ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:19:46Z"
    - latency: 2.289456ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 2.431126ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 2.323231ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 2.243652ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 2.161352ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:14:46Z"
    - latency: 2.436653ms
      message: 'network-check-target-ip-10-0-134-202: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-126-to-network-check-target-ip-10-0-139-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-126.ec2.internal
      uid: df882fdf-af6c-4bb6-86cf-b055e46a8830
    resourceVersion: "21973"
    uid: 0676976e-ab90-473a-a442-68b7d8527fdf
  spec:
    sourcePod: network-check-source-6f8b768455-jsp45
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T12:01:46Z"
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.171µs
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:22:46Z"
    - latency: 1.466572ms
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:21:46Z"
    - latency: 887.99µs
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:20:46Z"
    - latency: 883.952µs
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:19:46Z"
    - latency: 1.513254ms
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 852.813µs
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 1.347806ms
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 1.393174ms
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 897.442µs
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:14:46Z"
    - latency: 855.798µs
      message: 'network-check-target-ip-10-0-139-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-126-to-network-check-target-ip-10-0-142-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-126.ec2.internal
      uid: df882fdf-af6c-4bb6-86cf-b055e46a8830
    resourceVersion: "21974"
    uid: 7d8a7d63-8994-43a5-909f-276f7f3a146f
  spec:
    sourcePod: network-check-source-6f8b768455-jsp45
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T12:01:46Z"
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.363551ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:22:46Z"
    - latency: 2.213652ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:21:46Z"
    - latency: 2.08528ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:20:46Z"
    - latency: 2.1201ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:19:46Z"
    - latency: 1.998477ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 2.695911ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 2.463416ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 2.184805ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 2.262774ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:14:46Z"
    - latency: 2.002511ms
      message: 'network-check-target-ip-10-0-142-23: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-126-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-126.ec2.internal
      uid: df882fdf-af6c-4bb6-86cf-b055e46a8830
    resourceVersion: "20413"
    uid: 12180c9e-e867-48d3-b8d7-423d81898db6
  spec:
    sourcePod: network-check-source-6f8b768455-jsp45
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T12:00:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 753.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 2.332701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:18:46Z"
    - latency: 841.725µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 2.116949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:17:46Z"
    - latency: 909.502µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 1.734938ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:16:46Z"
    - latency: 855.287µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 2.257206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:15:46Z"
    - latency: 852.71µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:14:46Z"
    - latency: 1.573436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:14:46Z"
kind: List
metadata:
  resourceVersion: ""