apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-42.ec2.internal
      uid: 861cc96f-d114-4d68-ae8d-da9be425305d
    resourceVersion: "55031"
    uid: 9e2ff342-d630-43f6-a155-da0b30331a99
  spec:
    sourcePod: network-check-source-989f8b8dc-fzbff
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:38:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.166949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 882.634µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 1.069106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 968.73µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:07Z"
    - latency: 915.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:07Z"
    - latency: 1.565927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:07Z"
    - latency: 855.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:07Z"
    - latency: 1.014536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:07Z"
    - latency: 856.103µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:07Z"
    - latency: 930.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-42.ec2.internal
      uid: 861cc96f-d114-4d68-ae8d-da9be425305d
    resourceVersion: "55959"
    uid: 7a0e8789-d4bd-4290-9894-efc654d7d95a
  spec:
    sourcePod: network-check-source-989f8b8dc-fzbff
    targetEndpoint: a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:37:07Z"
      message: 'load-balancer-api-external: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.143757ms
      message: 'load-balancer-api-external: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:07:07Z"
    - latency: 7.055117ms
      message: 'load-balancer-api-external: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:07:07Z"
    - latency: 3.29617ms
      message: 'load-balancer-api-external: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 7.150135ms
      message: 'load-balancer-api-external: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 4.691356ms
      message: 'load-balancer-api-external: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 6.798334ms
      message: 'load-balancer-api-external: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 4.045551ms
      message: 'load-balancer-api-external: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 6.586843ms
      message: 'load-balancer-api-external: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 4.732751ms
      message: 'load-balancer-api-external: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:07Z"
    - latency: 7.03882ms
      message: 'load-balancer-api-external: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:03:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-42.ec2.internal
      uid: 861cc96f-d114-4d68-ae8d-da9be425305d
    resourceVersion: "55958"
    uid: 3fa64c25-efd9-4ba3-b987-9e0efbe94ce9
  spec:
    sourcePod: network-check-source-989f8b8dc-fzbff
    targetEndpoint: a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:37:07Z"
      message: 'load-balancer-api-internal: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.157464ms
      message: 'load-balancer-api-internal: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:07:07Z"
    - latency: 7.092399ms
      message: 'load-balancer-api-internal: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:07:07Z"
    - latency: 3.654765ms
      message: 'load-balancer-api-internal: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 7.222639ms
      message: 'load-balancer-api-internal: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 3.580247ms
      message: 'load-balancer-api-internal: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 6.887909ms
      message: 'load-balancer-api-internal: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 3.362224ms
      message: 'load-balancer-api-internal: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 6.634927ms
      message: 'load-balancer-api-internal: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 4.001787ms
      message: 'load-balancer-api-internal: tcp connection to a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:07Z"
    - latency: 7.131015ms
      message: 'load-balancer-api-internal: resolved host name a6ef97384509d4ad6aff53915b6cedbb-3fb2c87ed1a48548.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:03:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-42-to-network-check-target-ip-10-0-129-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-42.ec2.internal
      uid: 861cc96f-d114-4d68-ae8d-da9be425305d
    resourceVersion: "55028"
    uid: 099110b8-904c-4e2f-840c-d0a5af0cb0fd
  spec:
    sourcePod: network-check-source-989f8b8dc-fzbff
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:38:07Z"
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.965693ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 1.981743ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 2.341982ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 2.201294ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:07Z"
    - latency: 2.838676ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:07Z"
    - latency: 2.348034ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:07Z"
    - latency: 1.976769ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:07Z"
    - latency: 2.23252ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:07Z"
    - latency: 1.931964ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:07Z"
    - latency: 2.11064ms
      message: 'network-check-target-ip-10-0-129-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-42-to-network-check-target-ip-10-0-134-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-42.ec2.internal
      uid: 861cc96f-d114-4d68-ae8d-da9be425305d
    resourceVersion: "55029"
    uid: d73dccd2-3494-4860-b759-76898d76f10c
  spec:
    sourcePod: network-check-source-989f8b8dc-fzbff
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:38:07Z"
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.00761ms
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 870.474µs
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 1.028154ms
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 1.025002ms
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:07Z"
    - latency: 1.136853ms
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:07Z"
    - latency: 1.19016ms
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:07Z"
    - latency: 945.984µs
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:07Z"
    - latency: 980.377µs
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:07Z"
    - latency: 1.035245ms
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:07Z"
    - latency: 1.272492ms
      message: 'network-check-target-ip-10-0-134-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-42-to-network-check-target-ip-10-0-141-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-42.ec2.internal
      uid: 861cc96f-d114-4d68-ae8d-da9be425305d
    resourceVersion: "55030"
    uid: 39d30a80-a786-412e-b08e-9a469bb5380a
  spec:
    sourcePod: network-check-source-989f8b8dc-fzbff
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:38:07Z"
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.461497ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 2.150774ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 2.438994ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 2.289346ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:07Z"
    - latency: 2.5026ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:02:07Z"
    - latency: 2.383706ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:01:07Z"
    - latency: 2.46172ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:00:07Z"
    - latency: 2.661933ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:59:07Z"
    - latency: 2.076509ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:58:07Z"
    - latency: 2.323314ms
      message: 'network-check-target-ip-10-0-141-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:57:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-42.ec2.internal
      uid: 861cc96f-d114-4d68-ae8d-da9be425305d
    resourceVersion: "55955"
    uid: 27af2a80-44d8-46c5-83e2-59f9ff2aa849
  spec:
    sourcePod: network-check-source-989f8b8dc-fzbff
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:37:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.741µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:07:07Z"
    - latency: 2.20019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:07:07Z"
    - latency: 949.891µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 1.93518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:06:07Z"
    - latency: 941.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 1.788839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:05:07Z"
    - latency: 1.070386ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 1.857512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:04:07Z"
    - latency: 899.159µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T15:03:07Z"
    - latency: 1.949462ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T15:03:07Z"
kind: List
metadata:
  resourceVersion: ""