apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T15:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-168-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-168.ec2.internal
      uid: db4b9c8f-0e88-48c0-adf8-604cb4d93ac8
    resourceVersion: "51620"
    uid: 9d34d547-3073-4114-8cff-2143fd5e3cc7
  spec:
    sourcePod: network-check-source-869dcfcdcd-vqjfl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T15:45:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.924µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 1.101249ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 1.111724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 1.119771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:10:30Z"
    - latency: 849.545µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:09:30Z"
    - latency: 930.846µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:08:30Z"
    - latency: 805.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:07:30Z"
    - latency: 1.749518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:06:30Z"
    - latency: 960.428µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:05:30Z"
    - latency: 1.603523ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:04:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T15:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-168-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-168.ec2.internal
      uid: db4b9c8f-0e88-48c0-adf8-604cb4d93ac8
    resourceVersion: "52515"
    uid: 08a6c8bb-a4f1-4744-a97a-426f48e8f1aa
  spec:
    sourcePod: network-check-source-869dcfcdcd-vqjfl
    targetEndpoint: a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T15:44:30Z"
      message: 'load-balancer-api-external: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.3545ms
      message: 'load-balancer-api-external: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:14:30Z"
    - latency: 8.676904ms
      message: 'load-balancer-api-external: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:14:30Z"
    - latency: 7.401924ms
      message: 'load-balancer-api-external: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 8.679054ms
      message: 'load-balancer-api-external: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 5.196298ms
      message: 'load-balancer-api-external: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 8.278424ms
      message: 'load-balancer-api-external: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 6.501024ms
      message: 'load-balancer-api-external: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 7.968904ms
      message: 'load-balancer-api-external: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 4.284167ms
      message: 'load-balancer-api-external: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:10:30Z"
    - latency: 7.622494ms
      message: 'load-balancer-api-external: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:10:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T15:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-168-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-168.ec2.internal
      uid: db4b9c8f-0e88-48c0-adf8-604cb4d93ac8
    resourceVersion: "52516"
    uid: effcf628-c33b-4b1b-a946-713bccfca62a
  spec:
    sourcePod: network-check-source-869dcfcdcd-vqjfl
    targetEndpoint: a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T15:44:30Z"
      message: 'load-balancer-api-internal: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.717518ms
      message: 'load-balancer-api-internal: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:14:30Z"
    - latency: 8.687923ms
      message: 'load-balancer-api-internal: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:14:30Z"
    - latency: 4.636927ms
      message: 'load-balancer-api-internal: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 8.635962ms
      message: 'load-balancer-api-internal: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 5.123471ms
      message: 'load-balancer-api-internal: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 8.250198ms
      message: 'load-balancer-api-internal: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 3.730215ms
      message: 'load-balancer-api-internal: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 7.941097ms
      message: 'load-balancer-api-internal: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 3.536313ms
      message: 'load-balancer-api-internal: tcp connection to a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:10:30Z"
    - latency: 7.601236ms
      message: 'load-balancer-api-internal: resolved host name a03e03e86459047a090990137ee28e88-2a7d01fad290c1a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:10:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T15:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-168-to-network-check-target-ip-10-0-128-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-168.ec2.internal
      uid: db4b9c8f-0e88-48c0-adf8-604cb4d93ac8
    resourceVersion: "51619"
    uid: 96fb9d01-4a92-4cf5-81b6-fd6ab9ab845e
  spec:
    sourcePod: network-check-source-869dcfcdcd-vqjfl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T15:45:30Z"
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223338ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 1.815405ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 2.024507ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 1.887453ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:10:30Z"
    - latency: 1.721498ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:09:30Z"
    - latency: 1.71914ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:08:30Z"
    - latency: 1.914724ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:07:30Z"
    - latency: 2.444683ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:06:30Z"
    - latency: 2.002106ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:05:30Z"
    - latency: 2.000124ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:04:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T15:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-168-to-network-check-target-ip-10-0-134-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-168.ec2.internal
      uid: db4b9c8f-0e88-48c0-adf8-604cb4d93ac8
    resourceVersion: "51617"
    uid: 168b236a-2de6-4e83-94bc-f73f7a9ff1b8
  spec:
    sourcePod: network-check-source-869dcfcdcd-vqjfl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T15:45:30Z"
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.677µs
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 925.701µs
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 1.017652ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 1.515812ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:10:30Z"
    - latency: 878.219µs
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:09:30Z"
    - latency: 1.103363ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:08:30Z"
    - latency: 899.847µs
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:07:30Z"
    - latency: 1.019862ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:06:30Z"
    - latency: 1.061522ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:05:30Z"
    - latency: 1.769843ms
      message: 'network-check-target-ip-10-0-134-168: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:04:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T15:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-168-to-network-check-target-ip-10-0-141-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-168.ec2.internal
      uid: db4b9c8f-0e88-48c0-adf8-604cb4d93ac8
    resourceVersion: "51618"
    uid: 973ca387-9f21-48ea-9dbd-1e6a96798e87
  spec:
    sourcePod: network-check-source-869dcfcdcd-vqjfl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T15:45:30Z"
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.13027ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 1.904655ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 2.231852ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 2.502839ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:10:30Z"
    - latency: 2.496894ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:09:30Z"
    - latency: 1.98394ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:08:30Z"
    - latency: 1.958303ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:07:30Z"
    - latency: 2.538474ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:06:30Z"
    - latency: 2.48947ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:05:30Z"
    - latency: 2.12868ms
      message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:04:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T15:38:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-168-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-168.ec2.internal
      uid: db4b9c8f-0e88-48c0-adf8-604cb4d93ac8
    resourceVersion: "52513"
    uid: 0f1a2ddd-81af-443d-826d-6e735fed4ca7
  spec:
    sourcePod: network-check-source-869dcfcdcd-vqjfl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T15:44:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.922µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:14:30Z"
    - latency: 1.770177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:14:30Z"
    - latency: 1.162096ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 1.946003ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:13:30Z"
    - latency: 883.283µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 1.796808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:12:30Z"
    - latency: 730.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 1.654561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:11:30Z"
    - latency: 993.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T16:10:30Z"
    - latency: 2.34021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T16:10:30Z"
kind: List
metadata:
  resourceVersion: ""