apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T15:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-163-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-163.ec2.internal
      uid: b3148308-e2a6-4c0e-90c9-a81084c2ed38
    resourceVersion: "64558"
    uid: 9e5540db-e887-45f1-b1c6-247f37062781
  spec:
    sourcePod: network-check-source-7bc5b6bf85-m2c5r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T15:09:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.230624ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 1.416556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 909.298µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 1.325122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 2.033242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:40:05Z"
    - latency: 949.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:39:05Z"
    - latency: 913.881µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:38:05Z"
    - latency: 863.433µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:37:05Z"
    - latency: 1.281903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:36:05Z"
    - latency: 1.368872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:35:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T15:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-163-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-163.ec2.internal
      uid: b3148308-e2a6-4c0e-90c9-a81084c2ed38
    resourceVersion: "64560"
    uid: f3ed9e78-537b-494c-871c-ef89806e69b6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-m2c5r
    targetEndpoint: acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T15:08:05Z"
      message: 'load-balancer-api-external: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.719835ms
      message: 'load-balancer-api-external: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 7.240359ms
      message: 'load-balancer-api-external: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 4.260107ms
      message: 'load-balancer-api-external: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 6.486854ms
      message: 'load-balancer-api-external: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 5.482987ms
      message: 'load-balancer-api-external: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 7.377757ms
      message: 'load-balancer-api-external: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 3.897485ms
      message: 'load-balancer-api-external: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 7.696058ms
      message: 'load-balancer-api-external: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 5.936886ms
      message: 'load-balancer-api-external: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:40:05Z"
    - latency: 8.52314ms
      message: 'load-balancer-api-external: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:40:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T15:02:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-163-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-163.ec2.internal
      uid: b3148308-e2a6-4c0e-90c9-a81084c2ed38
    resourceVersion: "64559"
    uid: b783c8f5-358c-4b97-b54c-f260c9c4f43f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-m2c5r
    targetEndpoint: acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T15:08:05Z"
      message: 'load-balancer-api-internal: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.688467ms
      message: 'load-balancer-api-internal: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 7.261417ms
      message: 'load-balancer-api-internal: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 3.275579ms
      message: 'load-balancer-api-internal: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 6.543177ms
      message: 'load-balancer-api-internal: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 4.794656ms
      message: 'load-balancer-api-internal: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 7.563136ms
      message: 'load-balancer-api-internal: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 3.782791ms
      message: 'load-balancer-api-internal: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 7.726555ms
      message: 'load-balancer-api-internal: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 5.977016ms
      message: 'load-balancer-api-internal: tcp connection to acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:40:05Z"
    - latency: 8.552803ms
      message: 'load-balancer-api-internal: resolved host name acdead7fc76854d3ab49f77c728ae657-4710ef45738bb96b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:40:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T15:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-163-to-network-check-target-ip-10-0-138-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-163.ec2.internal
      uid: b3148308-e2a6-4c0e-90c9-a81084c2ed38
    resourceVersion: "64554"
    uid: 915fcc92-cea0-45ce-bc2d-20676a5a08b9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-m2c5r
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T15:09:05Z"
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.823077ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 1.91884ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 1.914749ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 1.981524ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 3.078617ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:40:05Z"
    - latency: 2.033077ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:39:05Z"
    - latency: 1.824767ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:38:05Z"
    - latency: 2.049734ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:37:05Z"
    - latency: 1.948527ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:36:05Z"
    - latency: 2.185241ms
      message: 'network-check-target-ip-10-0-138-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:35:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T15:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-163-to-network-check-target-ip-10-0-140-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-163.ec2.internal
      uid: b3148308-e2a6-4c0e-90c9-a81084c2ed38
    resourceVersion: "64553"
    uid: 8f00f5d5-77f8-478b-8327-b6830c19d39e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-m2c5r
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T15:09:05Z"
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.193µs
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 1.006165ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 1.362186ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 1.143643ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 1.452518ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:40:05Z"
    - latency: 1.240005ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:39:05Z"
    - latency: 941.12µs
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:38:05Z"
    - latency: 1.02198ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:37:05Z"
    - latency: 929.691µs
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:36:05Z"
    - latency: 988.251µs
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:35:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T15:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-163-to-network-check-target-ip-10-0-142-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-163.ec2.internal
      uid: b3148308-e2a6-4c0e-90c9-a81084c2ed38
    resourceVersion: "64555"
    uid: 9f0b072e-46ad-4956-8031-5d7da17da8a2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-m2c5r
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T15:09:05Z"
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.764987ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 2.038939ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 1.712697ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 2.217063ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 2.452926ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:40:05Z"
    - latency: 1.670691ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:39:05Z"
    - latency: 1.879698ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:38:05Z"
    - latency: 1.939287ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:37:05Z"
    - latency: 1.903862ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:36:05Z"
    - latency: 1.747625ms
      message: 'network-check-target-ip-10-0-142-31: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:35:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-19T15:02:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-163-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-163.ec2.internal
      uid: b3148308-e2a6-4c0e-90c9-a81084c2ed38
    resourceVersion: "64557"
    uid: 6737308f-1a27-4314-8c42-1eb09c9a2cf5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-m2c5r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-19T15:08:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.936µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 1.988991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:44:05Z"
    - latency: 838.942µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 2.204891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:43:05Z"
    - latency: 805.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 1.885523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:42:05Z"
    - latency: 909.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 2.235228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:41:05Z"
    - latency: 910.119µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-19T15:40:05Z"
    - latency: 2.783679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-19T15:40:05Z"
kind: List
metadata:
  resourceVersion: ""