apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: f626bf5d-bb50-4cb8-ba81-93b1de0ca309
    resourceVersion: "62741"
    uid: 468c6a8c-aa76-46c5-8007-af3d2c44b5f2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wjwsv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:01:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159547ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 1.101611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 1.304283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 1.082315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 1.146541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:32:05Z"
    - latency: 1.136546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:31:05Z"
    - latency: 1.181037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:30:05Z"
    - latency: 901.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:29:05Z"
    - latency: 920.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:28:05Z"
    - latency: 1.042967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: f626bf5d-bb50-4cb8-ba81-93b1de0ca309
    resourceVersion: "62743"
    uid: fca5065c-7b23-4366-b723-5dd35d0c432c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wjwsv
    targetEndpoint: a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:00:05Z"
      message: 'load-balancer-api-external: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.294338ms
      message: 'load-balancer-api-external: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 8.657709ms
      message: 'load-balancer-api-external: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 5.865293ms
      message: 'load-balancer-api-external: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 7.009015ms
      message: 'load-balancer-api-external: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 5.751994ms
      message: 'load-balancer-api-external: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 8.272481ms
      message: 'load-balancer-api-external: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 5.226439ms
      message: 'load-balancer-api-external: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 10.158167ms
      message: 'load-balancer-api-external: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 3.852261ms
      message: 'load-balancer-api-external: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:32:05Z"
    - latency: 9.570787ms
      message: 'load-balancer-api-external: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: f626bf5d-bb50-4cb8-ba81-93b1de0ca309
    resourceVersion: "62744"
    uid: 2e403d89-aa0b-42ef-b846-2c5b1db43de9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wjwsv
    targetEndpoint: a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:00:05Z"
      message: 'load-balancer-api-internal: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.74208ms
      message: 'load-balancer-api-internal: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 8.515436ms
      message: 'load-balancer-api-internal: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 5.564354ms
      message: 'load-balancer-api-internal: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 7.091233ms
      message: 'load-balancer-api-internal: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 5.745576ms
      message: 'load-balancer-api-internal: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 8.171674ms
      message: 'load-balancer-api-internal: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 4.732936ms
      message: 'load-balancer-api-internal: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 10.290712ms
      message: 'load-balancer-api-internal: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 5.455162ms
      message: 'load-balancer-api-internal: tcp connection to a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:32:05Z"
    - latency: 9.532182ms
      message: 'load-balancer-api-internal: resolved host name a3081720871e74d78bcb467e1c0bc94b-b4cf65111f59d038.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:32:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-ip-10-0-128-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: f626bf5d-bb50-4cb8-ba81-93b1de0ca309
    resourceVersion: "62739"
    uid: 4ee867e4-735e-4cf8-a667-75df14b3070c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wjwsv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:01:05Z"
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.497936ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 2.603435ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 2.553409ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 3.065697ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 2.895276ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:32:05Z"
    - latency: 2.447295ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:31:05Z"
    - latency: 2.519222ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:30:05Z"
    - latency: 2.651849ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:29:05Z"
    - latency: 2.304606ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:28:05Z"
    - latency: 2.662367ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-ip-10-0-130-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: f626bf5d-bb50-4cb8-ba81-93b1de0ca309
    resourceVersion: "62738"
    uid: 1649e98c-9bec-4dbf-9e27-17a17fc653d9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wjwsv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:01:05Z"
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.311834ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 2.445999ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 2.362831ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 2.53238ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 2.452694ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:32:05Z"
    - latency: 2.470723ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:31:05Z"
    - latency: 2.474936ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:30:05Z"
    - latency: 2.204596ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:29:05Z"
    - latency: 2.35079ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:28:05Z"
    - latency: 2.574759ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-ip-10-0-140-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: f626bf5d-bb50-4cb8-ba81-93b1de0ca309
    resourceVersion: "62737"
    uid: 1b73f172-e72f-44b1-8fa8-2973afd1d886
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wjwsv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:01:05Z"
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.37µs
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 1.015699ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 1.589697ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 1.114685ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 1.173027ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:32:05Z"
    - latency: 1.590085ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:31:05Z"
    - latency: 1.099696ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:30:05Z"
    - latency: 1.331566ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:29:05Z"
    - latency: 1.470826ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:28:05Z"
    - latency: 1.396385ms
      message: 'network-check-target-ip-10-0-140-67: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:27:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:54:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-67-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-67.ec2.internal
      uid: f626bf5d-bb50-4cb8-ba81-93b1de0ca309
    resourceVersion: "62740"
    uid: c10d3366-dc5d-4ff9-a727-a56b7a4516ab
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wjwsv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:00:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.261007ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 1.957234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:36:05Z"
    - latency: 946.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 1.974148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:35:05Z"
    - latency: 901.338µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 1.87566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:34:05Z"
    - latency: 895.808µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 1.847861ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:33:05Z"
    - latency: 784.072µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:32:05Z"
    - latency: 1.84499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:32:05Z"
kind: List
metadata:
  resourceVersion: ""