apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-62-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-62.ec2.internal
      uid: 9977dd86-4507-401f-8996-c5c8b41bca8c
    resourceVersion: "39283"
    uid: d53c44e6-15f1-4719-93e1-5878bf794023
  spec:
    sourcePod: network-check-source-869dcfcdcd-bdmq9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:35:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.144772ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:49:10Z"
    - latency: 1.256913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:48:10Z"
    - latency: 976.493µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:47:10Z"
    - latency: 747.226µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 1.250816ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 1.120707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 1.152798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 858.374µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:42:10Z"
    - latency: 783.756µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:41:10Z"
    - latency: 1.211058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:40:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-62-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-62.ec2.internal
      uid: 9977dd86-4507-401f-8996-c5c8b41bca8c
    resourceVersion: "36713"
    uid: d09152fb-46f7-4bc2-bcb0-b20bbec4cc9f
  spec:
    sourcePod: network-check-source-869dcfcdcd-bdmq9
    targetEndpoint: a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:34:10Z"
      message: 'load-balancer-api-external: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.679881ms
      message: 'load-balancer-api-external: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 8.455659ms
      message: 'load-balancer-api-external: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 4.127308ms
      message: 'load-balancer-api-external: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 9.210343ms
      message: 'load-balancer-api-external: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 3.408863ms
      message: 'load-balancer-api-external: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 9.783585ms
      message: 'load-balancer-api-external: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 5.004707ms
      message: 'load-balancer-api-external: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 8.484806ms
      message: 'load-balancer-api-external: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 3.901366ms
      message: 'load-balancer-api-external: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:42:10Z"
    - latency: 8.376544ms
      message: 'load-balancer-api-external: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:42:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-62-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-62.ec2.internal
      uid: 9977dd86-4507-401f-8996-c5c8b41bca8c
    resourceVersion: "36712"
    uid: 21c3cbdd-ceb1-4ef6-bb7d-cb881775e794
  spec:
    sourcePod: network-check-source-869dcfcdcd-bdmq9
    targetEndpoint: a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:34:10Z"
      message: 'load-balancer-api-internal: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.62298ms
      message: 'load-balancer-api-internal: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 8.407328ms
      message: 'load-balancer-api-internal: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 4.556898ms
      message: 'load-balancer-api-internal: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 9.136649ms
      message: 'load-balancer-api-internal: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 3.475359ms
      message: 'load-balancer-api-internal: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 9.734114ms
      message: 'load-balancer-api-internal: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 4.923042ms
      message: 'load-balancer-api-internal: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 8.37091ms
      message: 'load-balancer-api-internal: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 4.019652ms
      message: 'load-balancer-api-internal: tcp connection to a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:42:10Z"
    - latency: 8.327666ms
      message: 'load-balancer-api-internal: resolved host name a983901573f3a4713b65d2ce667c0d36-7e9b3f9d95647dcd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:42:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-62-to-network-check-target-ip-10-0-137-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-62.ec2.internal
      uid: 9977dd86-4507-401f-8996-c5c8b41bca8c
    resourceVersion: "39282"
    uid: 94827eae-d80c-4865-82f3-89fa1893d569
  spec:
    sourcePod: network-check-source-869dcfcdcd-bdmq9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:35:10Z"
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.310405ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:49:10Z"
    - latency: 2.052074ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:48:10Z"
    - latency: 2.087671ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:47:10Z"
    - latency: 2.040763ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 2.152974ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 2.087713ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 2.416719ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 2.313782ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:42:10Z"
    - latency: 2.150893ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:41:10Z"
    - latency: 1.906448ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:40:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-62-to-network-check-target-ip-10-0-141-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-62.ec2.internal
      uid: 9977dd86-4507-401f-8996-c5c8b41bca8c
    resourceVersion: "39281"
    uid: ced1ac4b-04d0-45f4-b2cb-6aef744be6ff
  spec:
    sourcePod: network-check-source-869dcfcdcd-bdmq9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:35:10Z"
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.329ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:49:10Z"
    - latency: 2.027932ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:48:10Z"
    - latency: 2.139989ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:47:10Z"
    - latency: 2.009465ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 2.452013ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 2.309585ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 2.122107ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 2.27116ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:42:10Z"
    - latency: 2.162572ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:41:10Z"
    - latency: 2.153315ms
      message: 'network-check-target-ip-10-0-141-225: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:40:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-62-to-network-check-target-ip-10-0-141-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-62.ec2.internal
      uid: 9977dd86-4507-401f-8996-c5c8b41bca8c
    resourceVersion: "39280"
    uid: 905f1331-1159-456a-aa09-6c4d9ab7c4cf
  spec:
    sourcePod: network-check-source-869dcfcdcd-bdmq9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:35:10Z"
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.484162ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:49:10Z"
    - latency: 1.100985ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:48:10Z"
    - latency: 1.09126ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:47:10Z"
    - latency: 848.332µs
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 1.464391ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 1.052757ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 795.918µs
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 1.619764ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:42:10Z"
    - latency: 968.464µs
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:41:10Z"
    - latency: 1.699101ms
      message: 'network-check-target-ip-10-0-141-62: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:40:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:28:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-62-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-62.ec2.internal
      uid: 9977dd86-4507-401f-8996-c5c8b41bca8c
    resourceVersion: "36711"
    uid: 9ca5fdac-fbaf-4fdd-8ffc-64840079f1af
  spec:
    sourcePod: network-check-source-869dcfcdcd-bdmq9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:34:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 2.000249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:46:10Z"
    - latency: 1.052061ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 2.13613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:45:10Z"
    - latency: 834.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 2.373787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:44:10Z"
    - latency: 1.03772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 1.791277ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:43:10Z"
    - latency: 1.086992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:42:10Z"
    - latency: 1.761054ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:42:10Z"
kind: List
metadata:
  resourceVersion: ""