apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-37.ec2.internal
      uid: 2870ff38-d3f5-4d29-b367-ad5aeb8fdff3
    resourceVersion: "62226"
    uid: efbf1832-8baa-4f6f-8858-e164e9ce113b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-l9994
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T12:37: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.026603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 1.200763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 1.011153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 1.059329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 940.215µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:08:46Z"
    - latency: 1.170853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:07:46Z"
    - latency: 1.189956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:06:46Z"
    - latency: 1.034311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:05:46Z"
    - latency: 1.414311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:04:46Z"
    - latency: 1.301838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-37.ec2.internal
      uid: 2870ff38-d3f5-4d29-b367-ad5aeb8fdff3
    resourceVersion: "62228"
    uid: 3bb0cd6e-6ce3-4e82-a319-1b2820c2199e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-l9994
    targetEndpoint: abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T12:36:46Z"
      message: 'load-balancer-api-external: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.438324ms
      message: 'load-balancer-api-external: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 7.211227ms
      message: 'load-balancer-api-external: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 3.815161ms
      message: 'load-balancer-api-external: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 6.316619ms
      message: 'load-balancer-api-external: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 4.960622ms
      message: 'load-balancer-api-external: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 9.871181ms
      message: 'load-balancer-api-external: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 5.112831ms
      message: 'load-balancer-api-external: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 8.273334ms
      message: 'load-balancer-api-external: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 5.626517ms
      message: 'load-balancer-api-external: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:08:46Z"
    - latency: 9.095299ms
      message: 'load-balancer-api-external: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:08:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-37.ec2.internal
      uid: 2870ff38-d3f5-4d29-b367-ad5aeb8fdff3
    resourceVersion: "62227"
    uid: b3705ec4-4ec3-4c38-ad43-1216a0d5021d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-l9994
    targetEndpoint: abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T12:36:46Z"
      message: 'load-balancer-api-internal: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.445715ms
      message: 'load-balancer-api-internal: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 7.156168ms
      message: 'load-balancer-api-internal: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 3.823ms
      message: 'load-balancer-api-internal: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 6.378148ms
      message: 'load-balancer-api-internal: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 4.988482ms
      message: 'load-balancer-api-internal: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 9.937314ms
      message: 'load-balancer-api-internal: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 5.083082ms
      message: 'load-balancer-api-internal: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 8.301256ms
      message: 'load-balancer-api-internal: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 5.626366ms
      message: 'load-balancer-api-internal: tcp connection to abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:08:46Z"
    - latency: 9.16821ms
      message: 'load-balancer-api-internal: resolved host name abc7011c60c364b819e36043c28b3a5d-99a9f7c206845434.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:08:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-37-to-network-check-target-ip-10-0-138-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-37.ec2.internal
      uid: 2870ff38-d3f5-4d29-b367-ad5aeb8fdff3
    resourceVersion: "62223"
    uid: 13f5ed99-2d06-4e0d-8356-c572979f16c0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-l9994
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T12:37:46Z"
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.79698ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 2.410396ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 2.470783ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 1.892333ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 2.394056ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:08:46Z"
    - latency: 2.392465ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:07:46Z"
    - latency: 2.551574ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:06:46Z"
    - latency: 2.508192ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:05:46Z"
    - latency: 2.392867ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:04:46Z"
    - latency: 2.4683ms
      message: 'network-check-target-ip-10-0-138-11: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-37-to-network-check-target-ip-10-0-140-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-37.ec2.internal
      uid: 2870ff38-d3f5-4d29-b367-ad5aeb8fdff3
    resourceVersion: "62222"
    uid: 542798eb-5f2a-49d8-a4f6-77ffaa1d5c58
  spec:
    sourcePod: network-check-source-7bc5b6bf85-l9994
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T12:37:46Z"
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.078µs
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 951.284µs
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 986.881µs
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 955.577µs
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 846.682µs
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:08:46Z"
    - latency: 960.855µs
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:07:46Z"
    - latency: 1.002763ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:06:46Z"
    - latency: 991.827µs
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:05:46Z"
    - latency: 1.62811ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:04:46Z"
    - latency: 1.338503ms
      message: 'network-check-target-ip-10-0-140-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-37-to-network-check-target-ip-10-0-143-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-37.ec2.internal
      uid: 2870ff38-d3f5-4d29-b367-ad5aeb8fdff3
    resourceVersion: "62224"
    uid: a0a4968e-af44-431e-ae98-a47522ce5533
  spec:
    sourcePod: network-check-source-7bc5b6bf85-l9994
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T12:37:46Z"
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.426954ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 2.418557ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 2.10877ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 2.231902ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 2.506043ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:08:46Z"
    - latency: 2.348301ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:07:46Z"
    - latency: 2.392149ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:06:46Z"
    - latency: 2.521042ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:05:46Z"
    - latency: 2.382391ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:04:46Z"
    - latency: 2.569178ms
      message: 'network-check-target-ip-10-0-143-161: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T12:30:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-37.ec2.internal
      uid: 2870ff38-d3f5-4d29-b367-ad5aeb8fdff3
    resourceVersion: "62225"
    uid: 61a7685a-fc9a-4339-8cea-0d2c0ac471ec
  spec:
    sourcePod: network-check-source-7bc5b6bf85-l9994
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T12:36:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030521ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 2.266117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:12:46Z"
    - latency: 863.801µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 1.673223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:11:46Z"
    - latency: 879.139µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 1.737737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:10:46Z"
    - latency: 963.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 1.64776ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:09:46Z"
    - latency: 936.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T13:08:46Z"
    - latency: 1.910714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T13:08:46Z"
kind: List
metadata:
  resourceVersion: ""