apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:07:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-63.us-west-1.compute.internal
      uid: 96b10448-f51f-4e2f-80a8-d2c6c1d2c6c8
    resourceVersion: "112576"
    uid: 071b7201-4747-47ec-a758-25a65b61b294
  spec:
    sourcePod: network-check-source-6f78d59f99-hq2vd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:14:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.344999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 1.739226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:09:39Z"
    - latency: 1.498043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:08:39Z"
    - latency: 1.373362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:07:39Z"
    - latency: 923.454µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:06:39Z"
    - latency: 826.319µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:05:39Z"
    - latency: 1.730743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:04:39Z"
    - latency: 1.033153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:39Z"
    - latency: 1.006009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:39Z"
    - latency: 1.362809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:07:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-63.us-west-1.compute.internal
      uid: 96b10448-f51f-4e2f-80a8-d2c6c1d2c6c8
    resourceVersion: "116656"
    uid: 57bd66e2-9995-41ec-b301-1594f89b8be1
  spec:
    sourcePod: network-check-source-6f78d59f99-hq2vd
    targetEndpoint: aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:13:39Z"
      message: 'load-balancer-api-external: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.47156ms
      message: 'load-balancer-api-external: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:13:39Z"
    - latency: 9.592514ms
      message: 'load-balancer-api-external: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:13:39Z"
    - latency: 55.379623ms
      message: 'load-balancer-api-external: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:12:39Z"
    - latency: 7.476934ms
      message: 'load-balancer-api-external: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:12:39Z"
    - latency: 54.799236ms
      message: 'load-balancer-api-external: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:11:39Z"
    - latency: 6.327727ms
      message: 'load-balancer-api-external: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:11:39Z"
    - latency: 54.886714ms
      message: 'load-balancer-api-external: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 6.822018ms
      message: 'load-balancer-api-external: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 55.358061ms
      message: 'load-balancer-api-external: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:09:39Z"
    - latency: 7.210084ms
      message: 'load-balancer-api-external: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:09:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:07:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-63.us-west-1.compute.internal
      uid: 96b10448-f51f-4e2f-80a8-d2c6c1d2c6c8
    resourceVersion: "116655"
    uid: 00070f1b-37a2-4c26-8e73-e9aa1f51fd52
  spec:
    sourcePod: network-check-source-6f78d59f99-hq2vd
    targetEndpoint: aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:13:39Z"
      message: 'load-balancer-api-internal: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.388847ms
      message: 'load-balancer-api-internal: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:13:39Z"
    - latency: 9.535459ms
      message: 'load-balancer-api-internal: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:13:39Z"
    - latency: 55.296012ms
      message: 'load-balancer-api-internal: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:12:39Z"
    - latency: 7.422525ms
      message: 'load-balancer-api-internal: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:12:39Z"
    - latency: 54.792361ms
      message: 'load-balancer-api-internal: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:11:39Z"
    - latency: 6.441905ms
      message: 'load-balancer-api-internal: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:11:39Z"
    - latency: 54.81358ms
      message: 'load-balancer-api-internal: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 6.738394ms
      message: 'load-balancer-api-internal: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 55.340287ms
      message: 'load-balancer-api-internal: tcp connection to aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:09:39Z"
    - latency: 7.25887ms
      message: 'load-balancer-api-internal: resolved host name aec41e53b5c24408ea18b6975af3dda9-0bfa0ebd3c963d0d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:09:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:07:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-63-to-network-check-target-ip-10-0-137-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-63.us-west-1.compute.internal
      uid: 96b10448-f51f-4e2f-80a8-d2c6c1d2c6c8
    resourceVersion: "112573"
    uid: 180c8c72-9071-4a1f-94b2-a98ebab31573
  spec:
    sourcePod: network-check-source-6f78d59f99-hq2vd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:14:39Z"
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.620584ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 2.736916ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:09:39Z"
    - latency: 2.138579ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:08:39Z"
    - latency: 3.102654ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:07:39Z"
    - latency: 2.051777ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:06:39Z"
    - latency: 2.395455ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:05:39Z"
    - latency: 2.506586ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:04:39Z"
    - latency: 2.332255ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:39Z"
    - latency: 2.190366ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:39Z"
    - latency: 2.046064ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:07:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-63-to-network-check-target-ip-10-0-141-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-63.us-west-1.compute.internal
      uid: 96b10448-f51f-4e2f-80a8-d2c6c1d2c6c8
    resourceVersion: "112569"
    uid: 703c03db-cbed-414d-a24c-81ec2c5de046
  spec:
    sourcePod: network-check-source-6f78d59f99-hq2vd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:14:39Z"
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.870209ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 1.044063ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:09:39Z"
    - latency: 1.401669ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:08:39Z"
    - latency: 1.911606ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:07:39Z"
    - latency: 2.81697ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:06:39Z"
    - latency: 1.180593ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:05:39Z"
    - latency: 1.047342ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:04:39Z"
    - latency: 926.969µs
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:39Z"
    - latency: 1.02438ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:39Z"
    - latency: 1.415573ms
      message: 'network-check-target-ip-10-0-141-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:07:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-63-to-network-check-target-ip-10-0-143-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-63.us-west-1.compute.internal
      uid: 96b10448-f51f-4e2f-80a8-d2c6c1d2c6c8
    resourceVersion: "112570"
    uid: 960ef7d1-c4c2-46cd-a12e-835815727317
  spec:
    sourcePod: network-check-source-6f78d59f99-hq2vd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:14:39Z"
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.603329ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 2.208722ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:09:39Z"
    - latency: 2.719164ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:08:39Z"
    - latency: 2.240235ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:07:39Z"
    - latency: 2.132809ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:06:39Z"
    - latency: 1.934569ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:05:39Z"
    - latency: 2.468196ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:04:39Z"
    - latency: 2.104892ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:03:39Z"
    - latency: 2.266925ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:02:39Z"
    - latency: 2.254666ms
      message: 'network-check-target-ip-10-0-143-53: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:01:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:07:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-63.us-west-1.compute.internal
      uid: 96b10448-f51f-4e2f-80a8-d2c6c1d2c6c8
    resourceVersion: "116653"
    uid: 8246831d-c52a-40bc-9703-1d98158a24bf
  spec:
    sourcePod: network-check-source-6f78d59f99-hq2vd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:13:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005948ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:13:39Z"
    - latency: 2.406585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:13:39Z"
    - latency: 1.080632ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:12:39Z"
    - latency: 2.337603ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:12:39Z"
    - latency: 991.774µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:11:39Z"
    - latency: 1.912311ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:11:39Z"
    - latency: 1.518575ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 2.028156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:10:39Z"
    - latency: 1.741531ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:09:39Z"
    - latency: 1.791719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:09:39Z"
kind: List
metadata:
  resourceVersion: ""