apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T00:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-34-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-34.ec2.internal
      uid: 3c3b9604-369b-4046-bcc3-d138e32a183b
    resourceVersion: "54437"
    uid: be49929b-c727-4f20-b3de-f02f9dbc4d53
  spec:
    sourcePod: network-check-source-685456655f-bpjjc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01: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: 840.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 1.207246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 756.286µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:20:46Z"
    - latency: 1.129805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:19:46Z"
    - latency: 1.060358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:18:46Z"
    - latency: 915.371µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:17:46Z"
    - latency: 773.242µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:16:46Z"
    - latency: 1.550219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:15:46Z"
    - latency: 1.084036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:14:46Z"
    - latency: 1.033015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T00:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-34-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-34.ec2.internal
      uid: 3c3b9604-369b-4046-bcc3-d138e32a183b
    resourceVersion: "56153"
    uid: cb535e75-11bd-4b46-bd80-00d8e27fc65f
  spec:
    sourcePod: network-check-source-685456655f-bpjjc
    targetEndpoint: a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:00:46Z"
      message: 'load-balancer-api-external: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.327359ms
      message: 'load-balancer-api-external: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:24:46Z"
    - latency: 9.262175ms
      message: 'load-balancer-api-external: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:24:46Z"
    - latency: 5.209017ms
      message: 'load-balancer-api-external: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:23:46Z"
    - latency: 11.553397ms
      message: 'load-balancer-api-external: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:23:46Z"
    - latency: 3.721502ms
      message: 'load-balancer-api-external: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 8.900274ms
      message: 'load-balancer-api-external: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 3.618745ms
      message: 'load-balancer-api-external: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 9.208517ms
      message: 'load-balancer-api-external: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 5.180602ms
      message: 'load-balancer-api-external: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:20:46Z"
    - latency: 7.618217ms
      message: 'load-balancer-api-external: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T00:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-34-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-34.ec2.internal
      uid: 3c3b9604-369b-4046-bcc3-d138e32a183b
    resourceVersion: "56154"
    uid: b78240c1-1817-4fe4-9067-996959eb96b2
  spec:
    sourcePod: network-check-source-685456655f-bpjjc
    targetEndpoint: a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:00:46Z"
      message: 'load-balancer-api-internal: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.376533ms
      message: 'load-balancer-api-internal: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:24:46Z"
    - latency: 9.357626ms
      message: 'load-balancer-api-internal: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:24:46Z"
    - latency: 5.208014ms
      message: 'load-balancer-api-internal: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:23:46Z"
    - latency: 11.576512ms
      message: 'load-balancer-api-internal: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:23:46Z"
    - latency: 3.363392ms
      message: 'load-balancer-api-internal: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 8.77284ms
      message: 'load-balancer-api-internal: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 3.180261ms
      message: 'load-balancer-api-internal: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 9.187973ms
      message: 'load-balancer-api-internal: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 5.20063ms
      message: 'load-balancer-api-internal: tcp connection to a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:20:46Z"
    - latency: 7.54464ms
      message: 'load-balancer-api-internal: resolved host name a433b964ace0e43caa3234d1bf0e48ca-508bcc8c00de52f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T00:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-34-to-network-check-target-ip-10-0-129-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-34.ec2.internal
      uid: 3c3b9604-369b-4046-bcc3-d138e32a183b
    resourceVersion: "54436"
    uid: 5e4a7b9e-77b3-4265-ad04-74c6c800269e
  spec:
    sourcePod: network-check-source-685456655f-bpjjc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:01:46Z"
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.254981ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 2.064997ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 1.949071ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:20:46Z"
    - latency: 2.300584ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:19:46Z"
    - latency: 2.324058ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:18:46Z"
    - latency: 2.189875ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:17:46Z"
    - latency: 2.248392ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:16:46Z"
    - latency: 2.236263ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:15:46Z"
    - latency: 2.040692ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:14:46Z"
    - latency: 2.457581ms
      message: 'network-check-target-ip-10-0-129-5: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T00:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-34-to-network-check-target-ip-10-0-130-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-34.ec2.internal
      uid: 3c3b9604-369b-4046-bcc3-d138e32a183b
    resourceVersion: "54434"
    uid: a2ef0b0b-6262-4f16-b84f-72cf178e484c
  spec:
    sourcePod: network-check-source-685456655f-bpjjc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:01:46Z"
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.098µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 1.060963ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 783.846µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:20:46Z"
    - latency: 770.478µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:19:46Z"
    - latency: 902.027µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:18:46Z"
    - latency: 796.407µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:17:46Z"
    - latency: 829.753µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:16:46Z"
    - latency: 722.449µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:15:46Z"
    - latency: 1.078119ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:14:46Z"
    - latency: 996.808µs
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T00:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-34-to-network-check-target-ip-10-0-140-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-34.ec2.internal
      uid: 3c3b9604-369b-4046-bcc3-d138e32a183b
    resourceVersion: "54435"
    uid: bf0b3ab8-de99-4026-9c41-97ff072403ce
  spec:
    sourcePod: network-check-source-685456655f-bpjjc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:01:46Z"
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.919254ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 1.84145ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 1.875526ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:20:46Z"
    - latency: 2.016702ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:19:46Z"
    - latency: 2.271704ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:18:46Z"
    - latency: 1.97245ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:17:46Z"
    - latency: 1.831724ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:16:46Z"
    - latency: 2.619222ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:15:46Z"
    - latency: 1.86896ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:14:46Z"
    - latency: 1.896995ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:13:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T00:54:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-34-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-34.ec2.internal
      uid: 3c3b9604-369b-4046-bcc3-d138e32a183b
    resourceVersion: "56152"
    uid: 40adcb11-f3cf-4711-b884-cd6dad7d12aa
  spec:
    sourcePod: network-check-source-685456655f-bpjjc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T01:00:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085742ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:24:46Z"
    - latency: 1.659088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:24:46Z"
    - latency: 1.64357ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:23:46Z"
    - latency: 3.008837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:23:46Z"
    - latency: 801.729µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 2.424373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:22:46Z"
    - latency: 943.057µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 1.81845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:21:46Z"
    - latency: 847.163µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T01:20:46Z"
    - latency: 1.732301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T01:20:46Z"
kind: List
metadata:
  resourceVersion: ""