apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:26:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-91-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-91.ec2.internal
      uid: 3bb091eb-c8f3-45b0-a6eb-7e6fe9dcdbb0
    resourceVersion: "60992"
    uid: 44840e34-0a8b-439b-b403-f6d5bbd84e05
  spec:
    sourcePod: network-check-source-869dcfcdcd-gg4gl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:33:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 817.101µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 939.241µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 1.050329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 954.797µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 808.538µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:04:02Z"
    - latency: 901.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:03:02Z"
    - latency: 1.089151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:02:02Z"
    - latency: 1.167063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:01:02Z"
    - latency: 993.171µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:00:02Z"
    - latency: 855.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:59:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:26:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-91-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-91.ec2.internal
      uid: 3bb091eb-c8f3-45b0-a6eb-7e6fe9dcdbb0
    resourceVersion: "60993"
    uid: 745ecb04-55dc-41e6-869b-9616971dd951
  spec:
    sourcePod: network-check-source-869dcfcdcd-gg4gl
    targetEndpoint: ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:32:02Z"
      message: 'load-balancer-api-external: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.605778ms
      message: 'load-balancer-api-external: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 8.020129ms
      message: 'load-balancer-api-external: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 6.792454ms
      message: 'load-balancer-api-external: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 8.447756ms
      message: 'load-balancer-api-external: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 4.546505ms
      message: 'load-balancer-api-external: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 7.768695ms
      message: 'load-balancer-api-external: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 4.566645ms
      message: 'load-balancer-api-external: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 7.125792ms
      message: 'load-balancer-api-external: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 4.065811ms
      message: 'load-balancer-api-external: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:04:02Z"
    - latency: 8.225364ms
      message: 'load-balancer-api-external: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:26:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-91-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-91.ec2.internal
      uid: 3bb091eb-c8f3-45b0-a6eb-7e6fe9dcdbb0
    resourceVersion: "60994"
    uid: c400c2ce-3456-43a0-b33a-14cbe17de1c0
  spec:
    sourcePod: network-check-source-869dcfcdcd-gg4gl
    targetEndpoint: ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:32:02Z"
      message: 'load-balancer-api-internal: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.620802ms
      message: 'load-balancer-api-internal: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 8.074534ms
      message: 'load-balancer-api-internal: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 5.762359ms
      message: 'load-balancer-api-internal: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 8.49872ms
      message: 'load-balancer-api-internal: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 4.757248ms
      message: 'load-balancer-api-internal: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 7.826065ms
      message: 'load-balancer-api-internal: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 4.522182ms
      message: 'load-balancer-api-internal: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 7.186181ms
      message: 'load-balancer-api-internal: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 3.496416ms
      message: 'load-balancer-api-internal: tcp connection to ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:04:02Z"
    - latency: 8.294076ms
      message: 'load-balancer-api-internal: resolved host name ab486752fcdd945ec979b047ae357c7d-ab0e033fbd523808.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:04:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:26:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-91-to-network-check-target-ip-10-0-132-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-91.ec2.internal
      uid: 3bb091eb-c8f3-45b0-a6eb-7e6fe9dcdbb0
    resourceVersion: "60991"
    uid: 334d6fdd-754a-4df1-97d6-b123111fdbe5
  spec:
    sourcePod: network-check-source-869dcfcdcd-gg4gl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:33:02Z"
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.538379ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 2.480196ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 2.555944ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 2.51418ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 3.039003ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:04:02Z"
    - latency: 2.538585ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:03:02Z"
    - latency: 2.903435ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:02:02Z"
    - latency: 2.64766ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:01:02Z"
    - latency: 2.48004ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:00:02Z"
    - latency: 2.546645ms
      message: 'network-check-target-ip-10-0-132-20: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:59:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:26:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-91-to-network-check-target-ip-10-0-137-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-91.ec2.internal
      uid: 3bb091eb-c8f3-45b0-a6eb-7e6fe9dcdbb0
    resourceVersion: "60989"
    uid: 0b13b65b-aa22-44f5-817c-db3804c3684b
  spec:
    sourcePod: network-check-source-869dcfcdcd-gg4gl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:33:02Z"
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.141224ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 2.19781ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 2.474384ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 2.406671ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 2.133378ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:04:02Z"
    - latency: 2.438406ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:03:02Z"
    - latency: 2.360736ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:02:02Z"
    - latency: 2.392711ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:01:02Z"
    - latency: 2.293193ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:00:02Z"
    - latency: 2.33244ms
      message: 'network-check-target-ip-10-0-137-89: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:59:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:26:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-91-to-network-check-target-ip-10-0-143-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-91.ec2.internal
      uid: 3bb091eb-c8f3-45b0-a6eb-7e6fe9dcdbb0
    resourceVersion: "60988"
    uid: 10d51a26-fd68-4cb4-904a-2cd9f94b8c83
  spec:
    sourcePod: network-check-source-869dcfcdcd-gg4gl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:33:02Z"
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 998.312µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 995.816µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 931.123µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 888.898µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 838.16µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:04:02Z"
    - latency: 1.140763ms
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:03:02Z"
    - latency: 831.439µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:02:02Z"
    - latency: 878.272µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:01:02Z"
    - latency: 804.636µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:00:02Z"
    - latency: 991.187µs
      message: 'network-check-target-ip-10-0-143-91: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T19:59:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T19:26:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-91-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-91.ec2.internal
      uid: 3bb091eb-c8f3-45b0-a6eb-7e6fe9dcdbb0
    resourceVersion: "60990"
    uid: ac4836ac-5a35-41cc-9f41-d83eca5de046
  spec:
    sourcePod: network-check-source-869dcfcdcd-gg4gl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T19:32:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020586ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 1.820132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:08:02Z"
    - latency: 874.668µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 1.604132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:07:02Z"
    - latency: 914.426µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 1.75488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:06:02Z"
    - latency: 1.087966ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 1.6847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:05:02Z"
    - latency: 821.442µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T20:04:02Z"
    - latency: 1.807907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T20:04:02Z"
kind: List
metadata:
  resourceVersion: ""