apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:42:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-226-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-226.ec2.internal
      uid: b2fe866a-453d-4856-a596-8c724052a75d
    resourceVersion: "53705"
    uid: a749230d-4762-4344-ae9f-d1990ec20d12
  spec:
    sourcePod: network-check-source-989f8b8dc-9hqbp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:49:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.307709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 1.323041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 935.999µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 978.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:01Z"
    - latency: 828.077µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:01Z"
    - latency: 1.081182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:01Z"
    - latency: 1.152409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:01Z"
    - latency: 822.393µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:01Z"
    - latency: 1.116899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:01Z"
    - latency: 1.030749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:42:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-226-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-226.ec2.internal
      uid: b2fe866a-453d-4856-a596-8c724052a75d
    resourceVersion: "54625"
    uid: a0663903-3560-41a4-a998-8042dea8341f
  spec:
    sourcePod: network-check-source-989f8b8dc-9hqbp
    targetEndpoint: aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:48:01Z"
      message: 'load-balancer-api-external: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.943745ms
      message: 'load-balancer-api-external: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:18:01Z"
    - latency: 15.763347ms
      message: 'load-balancer-api-external: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:18:01Z"
    - latency: 4.50101ms
      message: 'load-balancer-api-external: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 6.887345ms
      message: 'load-balancer-api-external: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 4.926125ms
      message: 'load-balancer-api-external: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 8.083064ms
      message: 'load-balancer-api-external: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 6.211676ms
      message: 'load-balancer-api-external: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 8.651262ms
      message: 'load-balancer-api-external: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 3.791956ms
      message: 'load-balancer-api-external: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:01Z"
    - latency: 16.924814ms
      message: 'load-balancer-api-external: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:42:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-226-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-226.ec2.internal
      uid: b2fe866a-453d-4856-a596-8c724052a75d
    resourceVersion: "54626"
    uid: 8f290c23-1184-42f7-8a30-f31144532ba3
  spec:
    sourcePod: network-check-source-989f8b8dc-9hqbp
    targetEndpoint: aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:48:01Z"
      message: 'load-balancer-api-internal: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.941233ms
      message: 'load-balancer-api-internal: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:18:01Z"
    - latency: 15.930876ms
      message: 'load-balancer-api-internal: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:18:01Z"
    - latency: 5.63079ms
      message: 'load-balancer-api-internal: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 6.796312ms
      message: 'load-balancer-api-internal: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 4.900918ms
      message: 'load-balancer-api-internal: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 8.132974ms
      message: 'load-balancer-api-internal: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 5.498299ms
      message: 'load-balancer-api-internal: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 8.548544ms
      message: 'load-balancer-api-internal: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 3.850843ms
      message: 'load-balancer-api-internal: tcp connection to aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:01Z"
    - latency: 16.908929ms
      message: 'load-balancer-api-internal: resolved host name aa41a14ec928448b7a73058468822869-d00c517117ce3846.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:42:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-226-to-network-check-target-ip-10-0-129-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-226.ec2.internal
      uid: b2fe866a-453d-4856-a596-8c724052a75d
    resourceVersion: "53704"
    uid: 8287fa29-6fae-47ea-8ccc-b35e102f5293
  spec:
    sourcePod: network-check-source-989f8b8dc-9hqbp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:49:01Z"
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.946405ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 2.325947ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 2.165196ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 2.118695ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:01Z"
    - latency: 1.754632ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:01Z"
    - latency: 2.232117ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:01Z"
    - latency: 2.190489ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:01Z"
    - latency: 1.730407ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:01Z"
    - latency: 2.059711ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:01Z"
    - latency: 1.959909ms
      message: 'network-check-target-ip-10-0-129-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:42:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-226-to-network-check-target-ip-10-0-129-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-226.ec2.internal
      uid: b2fe866a-453d-4856-a596-8c724052a75d
    resourceVersion: "53702"
    uid: 8a78ce22-6f55-49a7-9f3b-7b79e9b8c842
  spec:
    sourcePod: network-check-source-989f8b8dc-9hqbp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:49:01Z"
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.511µs
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 1.777581ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 980.808µs
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 1.29122ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:01Z"
    - latency: 744.646µs
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:01Z"
    - latency: 1.080389ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:01Z"
    - latency: 955.157µs
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:01Z"
    - latency: 928.027µs
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:01Z"
    - latency: 755.199µs
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:01Z"
    - latency: 1.045738ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:42:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-226-to-network-check-target-ip-10-0-136-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-226.ec2.internal
      uid: b2fe866a-453d-4856-a596-8c724052a75d
    resourceVersion: "53703"
    uid: 027bd94d-26d7-48f6-ab80-b4dfa02f8746
  spec:
    sourcePod: network-check-source-989f8b8dc-9hqbp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:49:01Z"
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.199034ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 2.511454ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 2.346377ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 2.512901ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:01Z"
    - latency: 1.744098ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:01Z"
    - latency: 2.175707ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:01Z"
    - latency: 2.585096ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:01Z"
    - latency: 2.113038ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:01Z"
    - latency: 2.289976ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:01Z"
    - latency: 2.156602ms
      message: 'network-check-target-ip-10-0-136-203: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:42:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-226-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-226.ec2.internal
      uid: b2fe866a-453d-4856-a596-8c724052a75d
    resourceVersion: "54624"
    uid: b38e3bc2-bcab-49a0-aec8-8195331a8612
  spec:
    sourcePod: network-check-source-989f8b8dc-9hqbp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:48:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.41243ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:18:01Z"
    - latency: 3.670517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:18:01Z"
    - latency: 954.465µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 1.912148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:17:01Z"
    - latency: 1.029518ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 2.324989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:01Z"
    - latency: 1.115344ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 2.339077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:01Z"
    - latency: 1.441501ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:01Z"
    - latency: 2.077873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:01Z"
kind: List
metadata:
  resourceVersion: ""