apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:52:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-145-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-145.ec2.internal
      uid: 774e5e7a-7236-4785-a4af-4b893d6fa7cd
    resourceVersion: "52535"
    uid: 3d836158-de99-4788-83c4-ffcfcf4b05e6
  spec:
    sourcePod: network-check-source-6f8b768455-twxgv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:59:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.065312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 1.368948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 1.051993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:23Z"
    - latency: 1.226174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:23Z"
    - latency: 1.085452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:23Z"
    - latency: 1.279892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:23Z"
    - latency: 1.030694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:23Z"
    - latency: 912.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:23Z"
    - latency: 1.235877ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:12:23Z"
    - latency: 915.692µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:52:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-145-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-145.ec2.internal
      uid: 774e5e7a-7236-4785-a4af-4b893d6fa7cd
    resourceVersion: "54311"
    uid: 16b46a30-b206-437e-a6f7-3d1f8b3c56d8
  spec:
    sourcePod: network-check-source-6f8b768455-twxgv
    targetEndpoint: ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:58:23Z"
      message: 'load-balancer-api-external: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.296744ms
      message: 'load-balancer-api-external: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:23Z"
    - latency: 9.312561ms
      message: 'load-balancer-api-external: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:22:23Z"
    - latency: 4.16356ms
      message: 'load-balancer-api-external: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:23Z"
    - latency: 8.460435ms
      message: 'load-balancer-api-external: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:21:23Z"
    - latency: 3.846186ms
      message: 'load-balancer-api-external: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 9.484089ms
      message: 'load-balancer-api-external: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 9.908922ms
      message: 'load-balancer-api-external: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 8.156364ms
      message: 'load-balancer-api-external: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 5.133939ms
      message: 'load-balancer-api-external: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:23Z"
    - latency: 9.120287ms
      message: 'load-balancer-api-external: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:52:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-145-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-145.ec2.internal
      uid: 774e5e7a-7236-4785-a4af-4b893d6fa7cd
    resourceVersion: "54312"
    uid: a65eb980-eed8-4303-a18b-2219607e86de
  spec:
    sourcePod: network-check-source-6f8b768455-twxgv
    targetEndpoint: ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:58:23Z"
      message: 'load-balancer-api-internal: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.306921ms
      message: 'load-balancer-api-internal: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:23Z"
    - latency: 9.24448ms
      message: 'load-balancer-api-internal: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:22:23Z"
    - latency: 5.281232ms
      message: 'load-balancer-api-internal: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:23Z"
    - latency: 8.48418ms
      message: 'load-balancer-api-internal: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:21:23Z"
    - latency: 4.017326ms
      message: 'load-balancer-api-internal: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 9.516567ms
      message: 'load-balancer-api-internal: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 5.962445ms
      message: 'load-balancer-api-internal: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 8.258037ms
      message: 'load-balancer-api-internal: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 4.789082ms
      message: 'load-balancer-api-internal: tcp connection to ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:23Z"
    - latency: 9.047229ms
      message: 'load-balancer-api-internal: resolved host name ad4db9e383bd2427892b2ca21b52e81f-2084099f92616d03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:52:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-145-to-network-check-target-ip-10-0-132-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-145.ec2.internal
      uid: 774e5e7a-7236-4785-a4af-4b893d6fa7cd
    resourceVersion: "52533"
    uid: bb174a6c-4dd6-4909-a275-5d9ec4f3d941
  spec:
    sourcePod: network-check-source-6f8b768455-twxgv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:59:23Z"
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.745316ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 1.890902ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 2.487951ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:23Z"
    - latency: 2.532226ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:23Z"
    - latency: 2.422362ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:23Z"
    - latency: 3.709498ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:23Z"
    - latency: 1.994814ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:23Z"
    - latency: 2.329491ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:23Z"
    - latency: 2.091269ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:12:23Z"
    - latency: 2.13768ms
      message: 'network-check-target-ip-10-0-132-170: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:52:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-145-to-network-check-target-ip-10-0-142-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-145.ec2.internal
      uid: 774e5e7a-7236-4785-a4af-4b893d6fa7cd
    resourceVersion: "52534"
    uid: 292f77e7-8bf9-4694-b31a-1756f81fc702
  spec:
    sourcePod: network-check-source-6f8b768455-twxgv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:59:23Z"
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.636µs
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 947.649µs
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 1.416044ms
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:23Z"
    - latency: 1.065353ms
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:23Z"
    - latency: 1.259104ms
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:23Z"
    - latency: 1.542778ms
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:23Z"
    - latency: 2.312014ms
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:23Z"
    - latency: 1.064866ms
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:23Z"
    - latency: 974.464µs
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:12:23Z"
    - latency: 984.061µs
      message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:52:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-145-to-network-check-target-ip-10-0-143-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-145.ec2.internal
      uid: 774e5e7a-7236-4785-a4af-4b893d6fa7cd
    resourceVersion: "52532"
    uid: 572dcddb-3a0c-4ae9-86fb-64393374d20d
  spec:
    sourcePod: network-check-source-6f8b768455-twxgv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:59:23Z"
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.58512ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 2.244375ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 2.459367ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:23Z"
    - latency: 2.532083ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:17:23Z"
    - latency: 2.745446ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:16:23Z"
    - latency: 2.604074ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:15:23Z"
    - latency: 2.489146ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:14:23Z"
    - latency: 2.383335ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:13:23Z"
    - latency: 2.402484ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:12:23Z"
    - latency: 2.189962ms
      message: 'network-check-target-ip-10-0-143-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T11:52:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-145-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-145.ec2.internal
      uid: 774e5e7a-7236-4785-a4af-4b893d6fa7cd
    resourceVersion: "54310"
    uid: dd7cd0d5-e93d-4fd7-b6aa-58ef7b30c39f
  spec:
    sourcePod: network-check-source-6f8b768455-twxgv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T11:58:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.907µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:22:23Z"
    - latency: 2.636999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:22:23Z"
    - latency: 948.462µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:21:23Z"
    - latency: 1.881993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:21:23Z"
    - latency: 920.561µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 1.947974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:20:23Z"
    - latency: 935.611µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 1.898227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:19:23Z"
    - latency: 967.442µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:18:23Z"
    - latency: 2.090342ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:18:23Z"
kind: List
metadata:
  resourceVersion: ""