apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:05:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-153-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-153.ec2.internal
      uid: 56ebb5d9-e24b-4ee3-a06e-3459dff3bddc
    resourceVersion: "55873"
    uid: 23935518-b0e4-40d0-8a3b-2cbd74ff0a1e
  spec:
    sourcePod: network-check-source-869dcfcdcd-8blf2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:12:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.340533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 863.737µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 1.17144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 1.063602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:26Z"
    - latency: 1.066146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:26Z"
    - latency: 1.069707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:26Z"
    - latency: 961.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:26Z"
    - latency: 844.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:26Z"
    - latency: 1.213945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:26Z"
    - latency: 977.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:05:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-153-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-153.ec2.internal
      uid: 56ebb5d9-e24b-4ee3-a06e-3459dff3bddc
    resourceVersion: "56824"
    uid: 49790119-892d-4d49-90ed-464149696d44
  spec:
    sourcePod: network-check-source-869dcfcdcd-8blf2
    targetEndpoint: a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:11:26Z"
      message: 'load-balancer-api-external: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.29242ms
      message: 'load-balancer-api-external: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:41:26Z"
    - latency: 6.98804ms
      message: 'load-balancer-api-external: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:41:26Z"
    - latency: 4.029966ms
      message: 'load-balancer-api-external: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 6.152612ms
      message: 'load-balancer-api-external: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 5.563567ms
      message: 'load-balancer-api-external: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 6.6308ms
      message: 'load-balancer-api-external: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 3.396037ms
      message: 'load-balancer-api-external: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 6.377128ms
      message: 'load-balancer-api-external: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 4.182075ms
      message: 'load-balancer-api-external: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:26Z"
    - latency: 6.504197ms
      message: 'load-balancer-api-external: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:05:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-153-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-153.ec2.internal
      uid: 56ebb5d9-e24b-4ee3-a06e-3459dff3bddc
    resourceVersion: "56825"
    uid: 289e444c-ed00-4a10-99bb-4585fc1dd221
  spec:
    sourcePod: network-check-source-869dcfcdcd-8blf2
    targetEndpoint: a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:11:26Z"
      message: 'load-balancer-api-internal: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.202685ms
      message: 'load-balancer-api-internal: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:41:26Z"
    - latency: 7.061552ms
      message: 'load-balancer-api-internal: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:41:26Z"
    - latency: 4.030382ms
      message: 'load-balancer-api-internal: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 6.260938ms
      message: 'load-balancer-api-internal: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 5.521849ms
      message: 'load-balancer-api-internal: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 6.584265ms
      message: 'load-balancer-api-internal: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 3.34185ms
      message: 'load-balancer-api-internal: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 6.444577ms
      message: 'load-balancer-api-internal: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 4.06077ms
      message: 'load-balancer-api-internal: tcp connection to a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:26Z"
    - latency: 6.620068ms
      message: 'load-balancer-api-internal: resolved host name a9f59d96a774f4bdeab3c207a6df696a-45d00755fa403492.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:05:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-153-to-network-check-target-ip-10-0-133-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-153.ec2.internal
      uid: 56ebb5d9-e24b-4ee3-a06e-3459dff3bddc
    resourceVersion: "55872"
    uid: ed2d882c-1b07-4c80-b200-f73dbedcc5fd
  spec:
    sourcePod: network-check-source-869dcfcdcd-8blf2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:12:26Z"
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.162749ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 2.238726ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 2.438646ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 2.277761ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:26Z"
    - latency: 2.32834ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:26Z"
    - latency: 2.388187ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:26Z"
    - latency: 2.057264ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:26Z"
    - latency: 2.123124ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:26Z"
    - latency: 2.492357ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:26Z"
    - latency: 2.418482ms
      message: 'network-check-target-ip-10-0-133-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:05:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-153-to-network-check-target-ip-10-0-139-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-153.ec2.internal
      uid: 56ebb5d9-e24b-4ee3-a06e-3459dff3bddc
    resourceVersion: "55871"
    uid: c4339659-3613-4aa4-afe8-f55daa8ba8a5
  spec:
    sourcePod: network-check-source-869dcfcdcd-8blf2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:12:26Z"
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.218867ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 2.24734ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 2.178893ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 2.401841ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:26Z"
    - latency: 2.38611ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:26Z"
    - latency: 2.566063ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:26Z"
    - latency: 2.169505ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:26Z"
    - latency: 2.809565ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:26Z"
    - latency: 2.497133ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:26Z"
    - latency: 2.356341ms
      message: 'network-check-target-ip-10-0-139-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:05:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-153-to-network-check-target-ip-10-0-140-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-153.ec2.internal
      uid: 56ebb5d9-e24b-4ee3-a06e-3459dff3bddc
    resourceVersion: "55870"
    uid: 19dfd3ea-8ab5-40e2-b081-bbc0c545e427
  spec:
    sourcePod: network-check-source-869dcfcdcd-8blf2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:12:26Z"
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.109481ms
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 918.273µs
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 1.06041ms
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 1.028698ms
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:26Z"
    - latency: 840.816µs
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:36:26Z"
    - latency: 866.458µs
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:35:26Z"
    - latency: 1.061509ms
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:34:26Z"
    - latency: 929.528µs
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:33:26Z"
    - latency: 993.926µs
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:26Z"
    - latency: 984.572µs
      message: 'network-check-target-ip-10-0-140-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T19:05:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-153-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-153.ec2.internal
      uid: 56ebb5d9-e24b-4ee3-a06e-3459dff3bddc
    resourceVersion: "56823"
    uid: 7a92d8c6-a226-45f1-b486-3d5cc5eaa243
  spec:
    sourcePod: network-check-source-869dcfcdcd-8blf2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:11:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 930.14µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:41:26Z"
    - latency: 1.733671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:41:26Z"
    - latency: 848.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 1.838476ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:40:26Z"
    - latency: 875.109µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 1.706136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:39:26Z"
    - latency: 886.458µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 1.770614ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:38:26Z"
    - latency: 893.261µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:37:26Z"
    - latency: 1.674127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:37:26Z"
kind: List
metadata:
  resourceVersion: ""