apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:32:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-104-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-104.ec2.internal
      uid: 4d409d66-2413-406a-bd0e-0a3af2189521
    resourceVersion: "63001"
    uid: 322cc657-446b-4e3e-bc92-1127e4cb9273
  spec:
    sourcePod: network-check-source-6f8b768455-qjvgh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:39:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 859.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 1.39634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 1.156332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:49Z"
    - latency: 1.123717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:49Z"
    - latency: 1.037902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:49Z"
    - latency: 940.798µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:49Z"
    - latency: 929.844µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:49Z"
    - latency: 1.334324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:49Z"
    - latency: 1.098129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:32:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-104-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-104.ec2.internal
      uid: 4d409d66-2413-406a-bd0e-0a3af2189521
    resourceVersion: "63724"
    uid: 089cc67e-01c3-4ed6-b525-cd5f42c8f2b6
  spec:
    sourcePod: network-check-source-6f8b768455-qjvgh
    targetEndpoint: aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:38:49Z"
      message: 'load-balancer-api-external: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.597763ms
      message: 'load-balancer-api-external: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:08:49Z"
    - latency: 8.819274ms
      message: 'load-balancer-api-external: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:08:49Z"
    - latency: 7.014125ms
      message: 'load-balancer-api-external: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 7.482593ms
      message: 'load-balancer-api-external: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 3.945374ms
      message: 'load-balancer-api-external: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 14.153674ms
      message: 'load-balancer-api-external: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 5.542898ms
      message: 'load-balancer-api-external: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 10.990652ms
      message: 'load-balancer-api-external: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 4.923155ms
      message: 'load-balancer-api-external: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:49Z"
    - latency: 7.64003ms
      message: 'load-balancer-api-external: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:04:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-104-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-104.ec2.internal
      uid: 4d409d66-2413-406a-bd0e-0a3af2189521
    resourceVersion: "63723"
    uid: eaeec8db-09dc-42af-bb66-ece07f339d15
  spec:
    sourcePod: network-check-source-6f8b768455-qjvgh
    targetEndpoint: aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:38:49Z"
      message: 'load-balancer-api-internal: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.607648ms
      message: 'load-balancer-api-internal: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:08:49Z"
    - latency: 8.782087ms
      message: 'load-balancer-api-internal: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:08:49Z"
    - latency: 6.148183ms
      message: 'load-balancer-api-internal: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 7.53792ms
      message: 'load-balancer-api-internal: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 3.952614ms
      message: 'load-balancer-api-internal: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 14.133579ms
      message: 'load-balancer-api-internal: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 11.52822ms
      message: 'load-balancer-api-internal: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 11.051155ms
      message: 'load-balancer-api-internal: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 4.816096ms
      message: 'load-balancer-api-internal: tcp connection to aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:49Z"
    - latency: 7.695984ms
      message: 'load-balancer-api-internal: resolved host name aa2a2cd1a3d4e43d0bde9fda70939a95-889843ab872114f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:04:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-104-to-network-check-target-ip-10-0-128-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-104.ec2.internal
      uid: 4d409d66-2413-406a-bd0e-0a3af2189521
    resourceVersion: "63000"
    uid: 29b1a521-657f-47e0-8db0-511725c71e08
  spec:
    sourcePod: network-check-source-6f8b768455-qjvgh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:39:49Z"
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.422803ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 2.437055ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 2.171352ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 2.292995ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:49Z"
    - latency: 2.488103ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:49Z"
    - latency: 2.33097ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:49Z"
    - latency: 2.277327ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:49Z"
    - latency: 2.691212ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:49Z"
    - latency: 2.45988ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:49Z"
    - latency: 2.209645ms
      message: 'network-check-target-ip-10-0-128-15: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-104-to-network-check-target-ip-10-0-134-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-104.ec2.internal
      uid: 4d409d66-2413-406a-bd0e-0a3af2189521
    resourceVersion: "62998"
    uid: d8a591ad-1431-4b90-be2d-fe637949e9f3
  spec:
    sourcePod: network-check-source-6f8b768455-qjvgh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:39:49Z"
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 963.985µs
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 1.698047ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 1.776684ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 1.024007ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:49Z"
    - latency: 1.467163ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:49Z"
    - latency: 1.201957ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:49Z"
    - latency: 976.316µs
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:49Z"
    - latency: 1.035167ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:49Z"
    - latency: 1.281465ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:49Z"
    - latency: 1.054356ms
      message: 'network-check-target-ip-10-0-134-104: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-104-to-network-check-target-ip-10-0-141-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-104.ec2.internal
      uid: 4d409d66-2413-406a-bd0e-0a3af2189521
    resourceVersion: "62999"
    uid: 8597baab-1951-4baa-aa74-a08caafda4a9
  spec:
    sourcePod: network-check-source-6f8b768455-qjvgh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:39:49Z"
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.587019ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 2.467834ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 2.074006ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 2.080093ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:49Z"
    - latency: 2.445985ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:03:49Z"
    - latency: 2.351718ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:02:49Z"
    - latency: 2.498382ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:01:49Z"
    - latency: 2.007431ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:00:49Z"
    - latency: 2.051409ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:59:49Z"
    - latency: 2.233651ms
      message: 'network-check-target-ip-10-0-141-17: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T15:58:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:32:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-104-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-104.ec2.internal
      uid: 4d409d66-2413-406a-bd0e-0a3af2189521
    resourceVersion: "63722"
    uid: 2278f6fe-5fa9-40d5-9047-e3fc1bf4cd36
  spec:
    sourcePod: network-check-source-6f8b768455-qjvgh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T15:38:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.883µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:08:49Z"
    - latency: 1.910018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:08:49Z"
    - latency: 934.129µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 2.159523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:07:49Z"
    - latency: 1.101685ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 2.066222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:06:49Z"
    - latency: 864.394µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 2.342473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:05:49Z"
    - latency: 1.102045ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:04:49Z"
    - latency: 1.942953ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:04:49Z"
kind: List
metadata:
  resourceVersion: ""