apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: e3803cfb-036f-454b-b491-30717ba1e3c9
    resourceVersion: "26762"
    uid: bdce9942-4b54-4213-8a32-54458ee090e6
  spec:
    sourcePod: network-check-source-989f8b8dc-srvdq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:05:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.232508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:12:41Z"
    - latency: 1.249759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:11:41Z"
    - latency: 1.159825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 1.025282ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 895.399µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 987.935µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 860.824µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:06:41Z"
    - latency: 1.122686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:05:41Z"
    - latency: 679.521µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:04:41Z"
    - latency: 949.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:03:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: e3803cfb-036f-454b-b491-30717ba1e3c9
    resourceVersion: "25552"
    uid: bc6aa05e-b0d5-4c01-91dc-630a7c0d37fc
  spec:
    sourcePod: network-check-source-989f8b8dc-srvdq
    targetEndpoint: abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:04:41Z"
      message: 'load-balancer-api-external: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.038786ms
      message: 'load-balancer-api-external: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 6.791744ms
      message: 'load-balancer-api-external: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 4.408809ms
      message: 'load-balancer-api-external: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 6.671645ms
      message: 'load-balancer-api-external: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 4.590138ms
      message: 'load-balancer-api-external: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 7.156903ms
      message: 'load-balancer-api-external: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 2.693337ms
      message: 'load-balancer-api-external: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 7.293787ms
      message: 'load-balancer-api-external: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 4.976894ms
      message: 'load-balancer-api-external: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:06:41Z"
    - latency: 6.474741ms
      message: 'load-balancer-api-external: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:06:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: e3803cfb-036f-454b-b491-30717ba1e3c9
    resourceVersion: "25553"
    uid: be326076-72e3-445d-8146-2e2c198f0c5b
  spec:
    sourcePod: network-check-source-989f8b8dc-srvdq
    targetEndpoint: abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:04:41Z"
      message: 'load-balancer-api-internal: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.086972ms
      message: 'load-balancer-api-internal: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 6.847347ms
      message: 'load-balancer-api-internal: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 4.462659ms
      message: 'load-balancer-api-internal: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 6.622201ms
      message: 'load-balancer-api-internal: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 4.555769ms
      message: 'load-balancer-api-internal: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 7.235875ms
      message: 'load-balancer-api-internal: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 4.292172ms
      message: 'load-balancer-api-internal: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 7.375239ms
      message: 'load-balancer-api-internal: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 4.548302ms
      message: 'load-balancer-api-internal: tcp connection to abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:06:41Z"
    - latency: 6.535346ms
      message: 'load-balancer-api-internal: resolved host name abace2619b70445ec99edd36c12223a5-3d9ecaa98d00b137.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:06:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-ip-10-0-128-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: e3803cfb-036f-454b-b491-30717ba1e3c9
    resourceVersion: "26759"
    uid: 79519601-8ebf-4adf-8ef5-d46a9830ff19
  spec:
    sourcePod: network-check-source-989f8b8dc-srvdq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:05:41Z"
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.739671ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:12:41Z"
    - latency: 1.798924ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:11:41Z"
    - latency: 2.013685ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 1.750367ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 1.793841ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 1.781031ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 1.723179ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:06:41Z"
    - latency: 1.682084ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:05:41Z"
    - latency: 1.590727ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:04:41Z"
    - latency: 1.945749ms
      message: 'network-check-target-ip-10-0-128-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:03:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-ip-10-0-139-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: e3803cfb-036f-454b-b491-30717ba1e3c9
    resourceVersion: "26760"
    uid: d3f2b5a1-bca5-4fb3-858a-bfecb5566621
  spec:
    sourcePod: network-check-source-989f8b8dc-srvdq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:05:41Z"
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.201986ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:12:41Z"
    - latency: 883.995µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:11:41Z"
    - latency: 871.484µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 780.092µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 1.082359ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 1.70824ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 909.15µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:06:41Z"
    - latency: 1.213389ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:05:41Z"
    - latency: 785.74µs
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:04:41Z"
    - latency: 1.301784ms
      message: 'network-check-target-ip-10-0-139-102: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:03:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-ip-10-0-142-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: e3803cfb-036f-454b-b491-30717ba1e3c9
    resourceVersion: "26761"
    uid: 173dd953-ffac-4103-92b0-1e797b3f235b
  spec:
    sourcePod: network-check-source-989f8b8dc-srvdq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:05:41Z"
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.064953ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:12:41Z"
    - latency: 2.253602ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:11:41Z"
    - latency: 2.059353ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 2.042899ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 2.240035ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 2.419913ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 2.29198ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:06:41Z"
    - latency: 2.447877ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:05:41Z"
    - latency: 2.137873ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:04:41Z"
    - latency: 2.087685ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:03:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T19:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-102.ec2.internal
      uid: e3803cfb-036f-454b-b491-30717ba1e3c9
    resourceVersion: "25551"
    uid: 65a55cf6-fe26-4b17-b585-fb67004cf8c4
  spec:
    sourcePod: network-check-source-989f8b8dc-srvdq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:04:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 1.658887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:10:41Z"
    - latency: 774.339µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 1.808718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:09:41Z"
    - latency: 773.884µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 2.040867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:08:41Z"
    - latency: 851.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 2.045996ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:07:41Z"
    - latency: 1.086125ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:06:41Z"
    - latency: 1.587507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:06:41Z"
kind: List
metadata:
  resourceVersion: ""