apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 0caa821f-7cbc-43af-b58e-1772fdad492c
    resourceVersion: "71625"
    uid: ab22eff7-75b3-4a0b-a71f-89ca159876a8
  spec:
    sourcePod: network-check-source-7d88cb55d8-9wwh4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:18:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.276µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:00:59Z"
    - latency: 1.650438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 1.096244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 985.313µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 1.270078ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 953.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:55:59Z"
    - latency: 1.07022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:54:59Z"
    - latency: 1.108189ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:53:59Z"
    - latency: 794.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:52:59Z"
    - latency: 1.26935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:51:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 0caa821f-7cbc-43af-b58e-1772fdad492c
    resourceVersion: "70532"
    uid: 9c21a4c6-e3a3-4d8b-9fd3-2dbeb7fc466f
  spec:
    sourcePod: network-check-source-7d88cb55d8-9wwh4
    targetEndpoint: a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:17:59Z"
      message: 'load-balancer-api-external: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.716391ms
      message: 'load-balancer-api-external: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 7.124242ms
      message: 'load-balancer-api-external: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 4.680296ms
      message: 'load-balancer-api-external: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 9.388234ms
      message: 'load-balancer-api-external: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 3.840737ms
      message: 'load-balancer-api-external: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 8.423607ms
      message: 'load-balancer-api-external: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 5.523194ms
      message: 'load-balancer-api-external: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 8.839126ms
      message: 'load-balancer-api-external: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 4.593491ms
      message: 'load-balancer-api-external: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:55:59Z"
    - latency: 8.192193ms
      message: 'load-balancer-api-external: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:55:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 0caa821f-7cbc-43af-b58e-1772fdad492c
    resourceVersion: "70533"
    uid: d2d0ebe5-c72a-445a-9a50-3b2ba9293a23
  spec:
    sourcePod: network-check-source-7d88cb55d8-9wwh4
    targetEndpoint: a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:17:59Z"
      message: 'load-balancer-api-internal: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.699766ms
      message: 'load-balancer-api-internal: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 7.189065ms
      message: 'load-balancer-api-internal: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 4.008542ms
      message: 'load-balancer-api-internal: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 9.303031ms
      message: 'load-balancer-api-internal: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 3.696911ms
      message: 'load-balancer-api-internal: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 8.367746ms
      message: 'load-balancer-api-internal: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 5.813722ms
      message: 'load-balancer-api-internal: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 8.758218ms
      message: 'load-balancer-api-internal: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 4.575411ms
      message: 'load-balancer-api-internal: tcp connection to a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:55:59Z"
    - latency: 8.147357ms
      message: 'load-balancer-api-internal: resolved host name a4e3a38fcf65b44c6997d4cdaa77a083-da7cf4870cfe7684.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:55:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-ip-10-0-130-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 0caa821f-7cbc-43af-b58e-1772fdad492c
    resourceVersion: "71624"
    uid: fa687762-b56c-466b-9f6d-334f0f840a6b
  spec:
    sourcePod: network-check-source-7d88cb55d8-9wwh4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:18:59Z"
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.207189ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:00:59Z"
    - latency: 2.432851ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 2.047935ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 2.200795ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 2.784887ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 2.155314ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:55:59Z"
    - latency: 1.812314ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:54:59Z"
    - latency: 1.89132ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:53:59Z"
    - latency: 1.920078ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:52:59Z"
    - latency: 2.091155ms
      message: 'network-check-target-ip-10-0-130-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:51:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-ip-10-0-132-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 0caa821f-7cbc-43af-b58e-1772fdad492c
    resourceVersion: "71622"
    uid: 843f800d-658d-4d3b-a445-02ec1e324cbb
  spec:
    sourcePod: network-check-source-7d88cb55d8-9wwh4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:18:59Z"
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.40886ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:00:59Z"
    - latency: 832.721µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 1.316831ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 1.313399ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 941.391µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 1.404589ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:55:59Z"
    - latency: 1.520568ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:54:59Z"
    - latency: 804.17µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:53:59Z"
    - latency: 1.500178ms
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:52:59Z"
    - latency: 931.043µs
      message: 'network-check-target-ip-10-0-132-129: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:51:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-ip-10-0-139-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 0caa821f-7cbc-43af-b58e-1772fdad492c
    resourceVersion: "71623"
    uid: 5d84f2ce-824b-4e1b-8a32-b0fc6a185c56
  spec:
    sourcePod: network-check-source-7d88cb55d8-9wwh4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:18:59Z"
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.457886ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:00:59Z"
    - latency: 2.532417ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 2.43268ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 2.307607ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 2.34887ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 2.406911ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:55:59Z"
    - latency: 2.372871ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:54:59Z"
    - latency: 2.364091ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:53:59Z"
    - latency: 2.179289ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:52:59Z"
    - latency: 2.320995ms
      message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:51:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-129-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-129.ec2.internal
      uid: 0caa821f-7cbc-43af-b58e-1772fdad492c
    resourceVersion: "70530"
    uid: b5c8a861-0216-48d3-b724-9a11f17e156b
  spec:
    sourcePod: network-check-source-7d88cb55d8-9wwh4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T15:17:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.298µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 1.705198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:59:59Z"
    - latency: 1.057918ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 2.075256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:58:59Z"
    - latency: 920.714µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 1.661613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:57:59Z"
    - latency: 1.196822ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 1.756972ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:56:59Z"
    - latency: 887.139µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T15:55:59Z"
    - latency: 1.674454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T15:55:59Z"
kind: List
metadata:
  resourceVersion: ""