apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: d7379d0f-ce73-45d5-9de7-bc9131a51e56
    resourceVersion: "64307"
    uid: 21d040a8-90e8-4859-962b-023e01f01640
  spec:
    sourcePod: network-check-source-7d88cb55d8-xvxgr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:53:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.341996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 1.535545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 986.382µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 1.084259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 1.426635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:24:42Z"
    - latency: 1.565964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:23:42Z"
    - latency: 952.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:22:42Z"
    - latency: 950.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:21:42Z"
    - latency: 1.077284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:20:42Z"
    - latency: 1.154466ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: d7379d0f-ce73-45d5-9de7-bc9131a51e56
    resourceVersion: "64309"
    uid: dd1da8c4-a7bb-47b7-8427-6862542b92b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-xvxgr
    targetEndpoint: a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:52:42Z"
      message: 'load-balancer-api-external: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.026116ms
      message: 'load-balancer-api-external: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 7.330218ms
      message: 'load-balancer-api-external: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 3.594884ms
      message: 'load-balancer-api-external: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 8.709705ms
      message: 'load-balancer-api-external: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 4.801575ms
      message: 'load-balancer-api-external: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 9.057057ms
      message: 'load-balancer-api-external: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 6.141462ms
      message: 'load-balancer-api-external: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 8.01974ms
      message: 'load-balancer-api-external: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 6.630033ms
      message: 'load-balancer-api-external: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:24:42Z"
    - latency: 7.829989ms
      message: 'load-balancer-api-external: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:24:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: d7379d0f-ce73-45d5-9de7-bc9131a51e56
    resourceVersion: "64308"
    uid: 9ee0ee78-0413-44a3-9c10-6a6c5272b0eb
  spec:
    sourcePod: network-check-source-7d88cb55d8-xvxgr
    targetEndpoint: a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:52:42Z"
      message: 'load-balancer-api-internal: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045356ms
      message: 'load-balancer-api-internal: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 7.469102ms
      message: 'load-balancer-api-internal: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 4.62826ms
      message: 'load-balancer-api-internal: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 8.793458ms
      message: 'load-balancer-api-internal: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 3.891734ms
      message: 'load-balancer-api-internal: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 8.992382ms
      message: 'load-balancer-api-internal: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 6.154531ms
      message: 'load-balancer-api-internal: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 7.951783ms
      message: 'load-balancer-api-internal: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 6.61748ms
      message: 'load-balancer-api-internal: tcp connection to a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:24:42Z"
    - latency: 8.010055ms
      message: 'load-balancer-api-internal: resolved host name a28fae654702e49d69374a7fc66c399b-ef654f4bbc4abc5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:24:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-134-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: d7379d0f-ce73-45d5-9de7-bc9131a51e56
    resourceVersion: "64303"
    uid: 6e634709-3a16-4743-bdf0-c976ad29bc9d
  spec:
    sourcePod: network-check-source-7d88cb55d8-xvxgr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:53:42Z"
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055136ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 1.056123ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 1.0439ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 1.41631ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 1.115863ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:24:42Z"
    - latency: 1.305316ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:23:42Z"
    - latency: 1.196258ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:22:42Z"
    - latency: 998.995µs
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:21:42Z"
    - latency: 1.158408ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:20:42Z"
    - latency: 1.239078ms
      message: 'network-check-target-ip-10-0-134-30: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-141-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: d7379d0f-ce73-45d5-9de7-bc9131a51e56
    resourceVersion: "64306"
    uid: d7fb841f-158f-4cad-a700-71c87e940188
  spec:
    sourcePod: network-check-source-7d88cb55d8-xvxgr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:53:42Z"
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.87384ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 2.077478ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 2.002394ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 2.134971ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 2.296108ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:24:42Z"
    - latency: 2.36159ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:23:42Z"
    - latency: 2.163608ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:22:42Z"
    - latency: 1.96821ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:21:42Z"
    - latency: 2.315611ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:20:42Z"
    - latency: 2.242255ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-ip-10-0-141-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: d7379d0f-ce73-45d5-9de7-bc9131a51e56
    resourceVersion: "64305"
    uid: 731e6a94-16a3-4919-8716-a142e9d83cac
  spec:
    sourcePod: network-check-source-7d88cb55d8-xvxgr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:53:42Z"
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382095ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 2.475296ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 2.170981ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 2.522629ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 2.354195ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:24:42Z"
    - latency: 2.339199ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:23:42Z"
    - latency: 1.742893ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:22:42Z"
    - latency: 2.383044ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:21:42Z"
    - latency: 2.248693ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:20:42Z"
    - latency: 2.613008ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T18:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-30.ec2.internal
      uid: d7379d0f-ce73-45d5-9de7-bc9131a51e56
    resourceVersion: "64304"
    uid: cf136af2-6001-474a-a5c9-aca527416884
  spec:
    sourcePod: network-check-source-7d88cb55d8-xvxgr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T18:52:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.059325ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 1.860368ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:28:42Z"
    - latency: 1.231146ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 1.770182ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:27:42Z"
    - latency: 1.063812ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 2.171024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:26:42Z"
    - latency: 1.134378ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 1.977713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:25:42Z"
    - latency: 1.047316ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T19:24:42Z"
    - latency: 2.113075ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T19:24:42Z"
kind: List
metadata:
  resourceVersion: ""