apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T01:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: 7d84c210-7080-4a90-9508-f471895cd558
    resourceVersion: "44946"
    uid: 32d0bc84-4c4e-49d0-8a1d-30e6226a21e8
  spec:
    sourcePod: network-check-source-7f44b6dd87-qwxlh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:59:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.04207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:20:30Z"
    - latency: 1.016092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:19:30Z"
    - latency: 1.418225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:18:30Z"
    - latency: 1.062386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:17:30Z"
    - latency: 1.170179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 1.521322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 1.076157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 1.077045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 979.916µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:12:30Z"
    - latency: 1.464201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:11:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T01:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: 7d84c210-7080-4a90-9508-f471895cd558
    resourceVersion: "40440"
    uid: 092c8f7c-8ee8-40fd-bdc1-80dc27bf7029
  spec:
    sourcePod: network-check-source-7f44b6dd87-qwxlh
    targetEndpoint: a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:58:30Z"
      message: 'load-balancer-api-external: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.73378ms
      message: 'load-balancer-api-external: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 6.128645ms
      message: 'load-balancer-api-external: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 4.746987ms
      message: 'load-balancer-api-external: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 11.639496ms
      message: 'load-balancer-api-external: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 3.755046ms
      message: 'load-balancer-api-external: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 8.616168ms
      message: 'load-balancer-api-external: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 5.127883ms
      message: 'load-balancer-api-external: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 6.568932ms
      message: 'load-balancer-api-external: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 5.26906ms
      message: 'load-balancer-api-external: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:12:30Z"
    - latency: 6.749526ms
      message: 'load-balancer-api-external: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:12:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T01:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: 7d84c210-7080-4a90-9508-f471895cd558
    resourceVersion: "40441"
    uid: f64654b4-d969-4cc1-974d-a58a675cd67f
  spec:
    sourcePod: network-check-source-7f44b6dd87-qwxlh
    targetEndpoint: a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:58:30Z"
      message: 'load-balancer-api-internal: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.688924ms
      message: 'load-balancer-api-internal: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 6.078365ms
      message: 'load-balancer-api-internal: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 3.284794ms
      message: 'load-balancer-api-internal: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 11.564241ms
      message: 'load-balancer-api-internal: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 3.757395ms
      message: 'load-balancer-api-internal: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 8.649443ms
      message: 'load-balancer-api-internal: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 4.18325ms
      message: 'load-balancer-api-internal: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 6.459885ms
      message: 'load-balancer-api-internal: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 5.253059ms
      message: 'load-balancer-api-internal: tcp connection to a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:12:30Z"
    - latency: 6.790943ms
      message: 'load-balancer-api-internal: resolved host name a59e8904fee944228b68b4a23ffce610-702a9aa549e03986.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:12:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T01:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-ip-10-0-129-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: 7d84c210-7080-4a90-9508-f471895cd558
    resourceVersion: "44945"
    uid: 6afc51cb-03e4-4dda-930e-7acf395b3b80
  spec:
    sourcePod: network-check-source-7f44b6dd87-qwxlh
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:59:30Z"
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.966537ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:20:30Z"
    - latency: 1.71228ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:19:30Z"
    - latency: 1.728376ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:18:30Z"
    - latency: 1.970609ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:17:30Z"
    - latency: 2.028508ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 2.017483ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 2.195631ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 1.869839ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 1.945399ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:12:30Z"
    - latency: 2.012623ms
      message: 'network-check-target-ip-10-0-129-167: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:11:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T01:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-ip-10-0-136-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: 7d84c210-7080-4a90-9508-f471895cd558
    resourceVersion: "44943"
    uid: 67742442-6851-43a4-aa1b-a75d8b2e6e02
  spec:
    sourcePod: network-check-source-7f44b6dd87-qwxlh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:59:30Z"
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.249481ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:20:30Z"
    - latency: 1.100189ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:19:30Z"
    - latency: 791.847µs
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:18:30Z"
    - latency: 1.215506ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:17:30Z"
    - latency: 1.068745ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 853.232µs
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 1.756464ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 840.871µs
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 1.155703ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:12:30Z"
    - latency: 1.463666ms
      message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:11:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T01:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-ip-10-0-141-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: 7d84c210-7080-4a90-9508-f471895cd558
    resourceVersion: "44944"
    uid: f3e4b7c1-c649-4b87-8b8c-59011eeea084
  spec:
    sourcePod: network-check-source-7f44b6dd87-qwxlh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:59:30Z"
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.34651ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:20:30Z"
    - latency: 2.146344ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:19:30Z"
    - latency: 1.946304ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:18:30Z"
    - latency: 2.235767ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:17:30Z"
    - latency: 2.043831ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 2.001811ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 2.186669ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 2.012219ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 2.12476ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:12:30Z"
    - latency: 2.39393ms
      message: 'network-check-target-ip-10-0-141-162: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:11:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T01:52:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-250-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-250.ec2.internal
      uid: 7d84c210-7080-4a90-9508-f471895cd558
    resourceVersion: "40439"
    uid: c92dc371-8e97-4ff1-9929-da9f50da5439
  spec:
    sourcePod: network-check-source-7f44b6dd87-qwxlh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T01:58:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.09439ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 1.727766ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:16:30Z"
    - latency: 1.066631ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 2.019055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:15:30Z"
    - latency: 975.768µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 1.387696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:14:30Z"
    - latency: 992.535µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 1.552091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:13:30Z"
    - latency: 937.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T02:12:30Z"
    - latency: 1.873393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T02:12:30Z"
kind: List
metadata:
  resourceVersion: ""