apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:10:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-4-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-4.ec2.internal
      uid: 39b9803c-fbdb-4e3a-ac87-d969305c48f6
    resourceVersion: "37887"
    uid: f1261de4-538d-4143-8704-f2cfc12a6a19
  spec:
    sourcePod: network-check-source-685456655f-qp5cj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:17:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 814.564µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 1.185011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 1.170814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:36:17Z"
    - latency: 1.219448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:35:17Z"
    - latency: 1.530588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:34:17Z"
    - latency: 798.431µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:33:17Z"
    - latency: 868.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:32:17Z"
    - latency: 1.171072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:31:17Z"
    - latency: 1.198755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:30:17Z"
    - latency: 1.168131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:10:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-4-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-4.ec2.internal
      uid: 39b9803c-fbdb-4e3a-ac87-d969305c48f6
    resourceVersion: "39409"
    uid: 3f52430b-3435-4513-85f2-69fd8867fccf
  spec:
    sourcePod: network-check-source-685456655f-qp5cj
    targetEndpoint: ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:16:17Z"
      message: 'load-balancer-api-external: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.786482ms
      message: 'load-balancer-api-external: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:40:17Z"
    - latency: 6.455441ms
      message: 'load-balancer-api-external: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:40:17Z"
    - latency: 5.105288ms
      message: 'load-balancer-api-external: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:39:17Z"
    - latency: 6.703529ms
      message: 'load-balancer-api-external: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:39:17Z"
    - latency: 4.176074ms
      message: 'load-balancer-api-external: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 6.615302ms
      message: 'load-balancer-api-external: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 4.966596ms
      message: 'load-balancer-api-external: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 5.79835ms
      message: 'load-balancer-api-external: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 4.71249ms
      message: 'load-balancer-api-external: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:36:17Z"
    - latency: 6.835412ms
      message: 'load-balancer-api-external: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:36:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:10:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-4-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-4.ec2.internal
      uid: 39b9803c-fbdb-4e3a-ac87-d969305c48f6
    resourceVersion: "39408"
    uid: e1e80558-eddc-4f60-9c91-a125e8483dd4
  spec:
    sourcePod: network-check-source-685456655f-qp5cj
    targetEndpoint: ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:16:17Z"
      message: 'load-balancer-api-internal: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.7457ms
      message: 'load-balancer-api-internal: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:40:17Z"
    - latency: 6.403226ms
      message: 'load-balancer-api-internal: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:40:17Z"
    - latency: 5.081195ms
      message: 'load-balancer-api-internal: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:39:17Z"
    - latency: 6.64545ms
      message: 'load-balancer-api-internal: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:39:17Z"
    - latency: 4.464871ms
      message: 'load-balancer-api-internal: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 6.552247ms
      message: 'load-balancer-api-internal: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 4.958484ms
      message: 'load-balancer-api-internal: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 5.774071ms
      message: 'load-balancer-api-internal: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 4.660871ms
      message: 'load-balancer-api-internal: tcp connection to ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:36:17Z"
    - latency: 6.8175ms
      message: 'load-balancer-api-internal: resolved host name ac520d6eb20c9434fabb08370c898293-caaea6c086f455b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:36:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:10:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-4-to-network-check-target-ip-10-0-130-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-4.ec2.internal
      uid: 39b9803c-fbdb-4e3a-ac87-d969305c48f6
    resourceVersion: "37886"
    uid: 58d0f25e-6398-4a0e-9b02-ae2c3d06393d
  spec:
    sourcePod: network-check-source-685456655f-qp5cj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:17:17Z"
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.867404ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 2.034189ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 1.940462ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:36:17Z"
    - latency: 2.05489ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:35:17Z"
    - latency: 1.960857ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:34:17Z"
    - latency: 1.765075ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:33:17Z"
    - latency: 2.071563ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:32:17Z"
    - latency: 2.042083ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:31:17Z"
    - latency: 2.013949ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:30:17Z"
    - latency: 2.044793ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:10:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-4-to-network-check-target-ip-10-0-130-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-4.ec2.internal
      uid: 39b9803c-fbdb-4e3a-ac87-d969305c48f6
    resourceVersion: "37885"
    uid: 9f161828-4bcd-43ef-8f10-7894a3e04304
  spec:
    sourcePod: network-check-source-685456655f-qp5cj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:17:17Z"
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.002477ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 2.381249ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 2.408385ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:36:17Z"
    - latency: 2.036852ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:35:17Z"
    - latency: 2.203065ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:34:17Z"
    - latency: 2.038931ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:33:17Z"
    - latency: 2.037999ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:32:17Z"
    - latency: 2.466739ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:31:17Z"
    - latency: 2.367149ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:30:17Z"
    - latency: 2.155067ms
      message: 'network-check-target-ip-10-0-130-30: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:10:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-4-to-network-check-target-ip-10-0-139-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-4.ec2.internal
      uid: 39b9803c-fbdb-4e3a-ac87-d969305c48f6
    resourceVersion: "37884"
    uid: 1d1c93d0-0af7-4651-95e9-73bb02206746
  spec:
    sourcePod: network-check-source-685456655f-qp5cj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:17:17Z"
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013434ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 850.515µs
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 983.462µs
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:36:17Z"
    - latency: 870.922µs
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:35:17Z"
    - latency: 824.424µs
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:34:17Z"
    - latency: 703.583µs
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:33:17Z"
    - latency: 1.138822ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:32:17Z"
    - latency: 1.001828ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:31:17Z"
    - latency: 1.121701ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:30:17Z"
    - latency: 1.377493ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:29:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T06:10:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-4-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-4.ec2.internal
      uid: 39b9803c-fbdb-4e3a-ac87-d969305c48f6
    resourceVersion: "39407"
    uid: 439daa98-311b-4319-b6ba-544bbda89770
  spec:
    sourcePod: network-check-source-685456655f-qp5cj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T06:16:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.023µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:40:17Z"
    - latency: 1.740717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:40:17Z"
    - latency: 1.211776ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:39:17Z"
    - latency: 1.861338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:39:17Z"
    - latency: 1.031452ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 2.029553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:38:17Z"
    - latency: 866.228µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 1.795826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:37:17Z"
    - latency: 929.11µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T06:36:17Z"
    - latency: 1.848494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T06:36:17Z"
kind: List
metadata:
  resourceVersion: ""