apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T16:27:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 970615b7-4daf-43be-b1c2-8466c6006ac1
    resourceVersion: "55166"
    uid: 950c5ab6-58da-4792-a430-1ebfcbf1d6a3
  spec:
    sourcePod: network-check-source-869dcfcdcd-b9gjz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T16:34:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.095218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 1.048373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 944.778µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 1.48519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:59:33Z"
    - latency: 1.213923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:58:33Z"
    - latency: 1.123271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:57:33Z"
    - latency: 828.546µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:56:33Z"
    - latency: 863.155µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:55:33Z"
    - latency: 851.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:54:33Z"
    - latency: 933.216µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:53:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T16:27:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 970615b7-4daf-43be-b1c2-8466c6006ac1
    resourceVersion: "56215"
    uid: 3f788d32-f19a-43c7-a9dc-a6ec798fbfec
  spec:
    sourcePod: network-check-source-869dcfcdcd-b9gjz
    targetEndpoint: a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T16:33:33Z"
      message: 'load-balancer-api-external: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.657404ms
      message: 'load-balancer-api-external: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:03:33Z"
    - latency: 7.449664ms
      message: 'load-balancer-api-external: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:03:33Z"
    - latency: 4.799555ms
      message: 'load-balancer-api-external: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 8.798576ms
      message: 'load-balancer-api-external: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 6.054869ms
      message: 'load-balancer-api-external: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 8.799491ms
      message: 'load-balancer-api-external: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 4.028702ms
      message: 'load-balancer-api-external: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 9.105679ms
      message: 'load-balancer-api-external: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 4.449919ms
      message: 'load-balancer-api-external: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:59:33Z"
    - latency: 11.088416ms
      message: 'load-balancer-api-external: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:59:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T16:27:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 970615b7-4daf-43be-b1c2-8466c6006ac1
    resourceVersion: "56214"
    uid: e3a6564f-f607-41b1-8fc5-81da5053e931
  spec:
    sourcePod: network-check-source-869dcfcdcd-b9gjz
    targetEndpoint: a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T16:33:33Z"
      message: 'load-balancer-api-internal: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.305119ms
      message: 'load-balancer-api-internal: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:03:33Z"
    - latency: 7.495737ms
      message: 'load-balancer-api-internal: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:03:33Z"
    - latency: 4.760015ms
      message: 'load-balancer-api-internal: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 8.735977ms
      message: 'load-balancer-api-internal: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 6.111969ms
      message: 'load-balancer-api-internal: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 8.747189ms
      message: 'load-balancer-api-internal: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 4.086383ms
      message: 'load-balancer-api-internal: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 9.039258ms
      message: 'load-balancer-api-internal: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 4.262769ms
      message: 'load-balancer-api-internal: tcp connection to a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:59:33Z"
    - latency: 11.028626ms
      message: 'load-balancer-api-internal: resolved host name a7721f226c67a4c46bcefa88922d75ea-cdc6194418ed376b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:59:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T16:27:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-ip-10-0-132-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 970615b7-4daf-43be-b1c2-8466c6006ac1
    resourceVersion: "55165"
    uid: df9b8a97-c027-48b9-b1d3-4ebff2b3a9e7
  spec:
    sourcePod: network-check-source-869dcfcdcd-b9gjz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T16:34:33Z"
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.557992ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 2.420808ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 2.483787ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 2.172092ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:59:33Z"
    - latency: 2.187742ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:58:33Z"
    - latency: 2.115816ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:57:33Z"
    - latency: 2.051972ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:56:33Z"
    - latency: 2.433549ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:55:33Z"
    - latency: 2.705606ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:54:33Z"
    - latency: 2.248291ms
      message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:53:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T16:27:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-ip-10-0-134-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 970615b7-4daf-43be-b1c2-8466c6006ac1
    resourceVersion: "55164"
    uid: 6f6e0cbb-53fa-48ec-aa5e-150ef7e38192
  spec:
    sourcePod: network-check-source-869dcfcdcd-b9gjz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T16:34:33Z"
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.582251ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 2.779665ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 2.547147ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 2.381536ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:59:33Z"
    - latency: 2.635169ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:58:33Z"
    - latency: 2.581091ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:57:33Z"
    - latency: 2.337913ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:56:33Z"
    - latency: 2.428582ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:55:33Z"
    - latency: 2.676907ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:54:33Z"
    - latency: 2.31005ms
      message: 'network-check-target-ip-10-0-134-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:53:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T16:27:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-ip-10-0-141-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 970615b7-4daf-43be-b1c2-8466c6006ac1
    resourceVersion: "55163"
    uid: 1fc9ab99-7af9-48c3-930f-adf3ce763b35
  spec:
    sourcePod: network-check-source-869dcfcdcd-b9gjz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T16:34:33Z"
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.074927ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 1.445797ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 1.088193ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 963.691µs
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:59:33Z"
    - latency: 1.028381ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:58:33Z"
    - latency: 833.04µs
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:57:33Z"
    - latency: 1.466042ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:56:33Z"
    - latency: 1.218924ms
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:55:33Z"
    - latency: 883.165µs
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:54:33Z"
    - latency: 846.325µs
      message: 'network-check-target-ip-10-0-141-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:53:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T16:27:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-8.ec2.internal
      uid: 970615b7-4daf-43be-b1c2-8466c6006ac1
    resourceVersion: "56213"
    uid: 81e3c13e-a29a-4f1c-bf82-0e37853e089e
  spec:
    sourcePod: network-check-source-869dcfcdcd-b9gjz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T16:33:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.785µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:03:33Z"
    - latency: 1.552316ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:03:33Z"
    - latency: 919.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 2.103785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:02:33Z"
    - latency: 1.120887ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 1.782342ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:01:33Z"
    - latency: 1.239016ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 1.722785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:00:33Z"
    - latency: 1.311522ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T16:59:33Z"
    - latency: 1.916759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T16:59:33Z"
kind: List
metadata:
  resourceVersion: ""