apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-0.ec2.internal
      uid: fe5a111d-6f10-4e1b-8ba7-3baf137b0292
    resourceVersion: "66995"
    uid: e1272d64-c8a7-4e7b-87e4-71792199bb5b
  spec:
    sourcePod: network-check-source-6f8b768455-d7lrt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:29:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.328701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:57:24Z"
    - latency: 1.33671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:56:24Z"
    - latency: 1.219354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:55:24Z"
    - latency: 1.239795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:54:24Z"
    - latency: 1.110251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:53:24Z"
    - latency: 1.246243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 1.201096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 1.068614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 1.077905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 1.035869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:48:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-0.ec2.internal
      uid: fe5a111d-6f10-4e1b-8ba7-3baf137b0292
    resourceVersion: "62825"
    uid: b446ea28-0ca8-4174-bfe1-6c955439c895
  spec:
    sourcePod: network-check-source-6f8b768455-d7lrt
    targetEndpoint: a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:28:24Z"
      message: 'load-balancer-api-external: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.519883ms
      message: 'load-balancer-api-external: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 8.886467ms
      message: 'load-balancer-api-external: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 4.023585ms
      message: 'load-balancer-api-external: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 13.794891ms
      message: 'load-balancer-api-external: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 4.783602ms
      message: 'load-balancer-api-external: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 8.239303ms
      message: 'load-balancer-api-external: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 4.87358ms
      message: 'load-balancer-api-external: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 8.462248ms
      message: 'load-balancer-api-external: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 3.919646ms
      message: 'load-balancer-api-external: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:48:24Z"
    - latency: 10.279896ms
      message: 'load-balancer-api-external: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:48:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-0.ec2.internal
      uid: fe5a111d-6f10-4e1b-8ba7-3baf137b0292
    resourceVersion: "62826"
    uid: 7e793640-4087-40ba-a8a5-c60c4e0fbe88
  spec:
    sourcePod: network-check-source-6f8b768455-d7lrt
    targetEndpoint: a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:28:24Z"
      message: 'load-balancer-api-internal: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.578178ms
      message: 'load-balancer-api-internal: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 8.974565ms
      message: 'load-balancer-api-internal: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 4.014452ms
      message: 'load-balancer-api-internal: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 13.862886ms
      message: 'load-balancer-api-internal: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 4.774831ms
      message: 'load-balancer-api-internal: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 8.338999ms
      message: 'load-balancer-api-internal: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 3.999365ms
      message: 'load-balancer-api-internal: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 8.517323ms
      message: 'load-balancer-api-internal: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 5.161234ms
      message: 'load-balancer-api-internal: tcp connection to a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:48:24Z"
    - latency: 7.624186ms
      message: 'load-balancer-api-internal: resolved host name a3ca4ed61eb2b47c8baa89ac5ab83b0f-007e76e6d0683d83.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:48:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-0-to-network-check-target-ip-10-0-135-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-0.ec2.internal
      uid: fe5a111d-6f10-4e1b-8ba7-3baf137b0292
    resourceVersion: "66994"
    uid: b1c614cb-b197-4e78-9c7a-a2a44b1f2dce
  spec:
    sourcePod: network-check-source-6f8b768455-d7lrt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:29:24Z"
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.612991ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:57:24Z"
    - latency: 2.536412ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:56:24Z"
    - latency: 2.559376ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:55:24Z"
    - latency: 2.476353ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:54:24Z"
    - latency: 2.36559ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:53:24Z"
    - latency: 2.41097ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 2.464884ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 2.185295ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 2.374933ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 2.261512ms
      message: 'network-check-target-ip-10-0-135-147: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:48:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-0-to-network-check-target-ip-10-0-138-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-0.ec2.internal
      uid: fe5a111d-6f10-4e1b-8ba7-3baf137b0292
    resourceVersion: "66993"
    uid: e2d14e5c-ed93-4a64-b05c-77b992e73c13
  spec:
    sourcePod: network-check-source-6f8b768455-d7lrt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:29:24Z"
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.41368ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:57:24Z"
    - latency: 2.537505ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:56:24Z"
    - latency: 1.81043ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:55:24Z"
    - latency: 2.419902ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:54:24Z"
    - latency: 2.29236ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:53:24Z"
    - latency: 2.597254ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 2.440092ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 2.036022ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 2.363338ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 2.828525ms
      message: 'network-check-target-ip-10-0-138-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:48:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-0-to-network-check-target-ip-10-0-141-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-0.ec2.internal
      uid: fe5a111d-6f10-4e1b-8ba7-3baf137b0292
    resourceVersion: "66992"
    uid: cb65d4ac-f522-412f-a3c5-13ff2b4f1cd9
  spec:
    sourcePod: network-check-source-6f8b768455-d7lrt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:29:24Z"
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.009034ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:57:24Z"
    - latency: 1.393541ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:56:24Z"
    - latency: 1.355282ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:55:24Z"
    - latency: 1.348616ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:54:24Z"
    - latency: 1.025795ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:53:24Z"
    - latency: 827.631µs
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 931.42µs
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 980.849µs
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 1.101097ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 1.650712ms
      message: 'network-check-target-ip-10-0-141-0: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:48:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T19:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-0.ec2.internal
      uid: fe5a111d-6f10-4e1b-8ba7-3baf137b0292
    resourceVersion: "62824"
    uid: f0ec6331-5455-4091-8f1b-4a83de6febc4
  spec:
    sourcePod: network-check-source-6f8b768455-d7lrt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T19:28:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 779.223µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 1.652432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:52:24Z"
    - latency: 904.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 2.317269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:51:24Z"
    - latency: 1.108139ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 1.891778ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:50:24Z"
    - latency: 842.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 1.752709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:49:24Z"
    - latency: 1.810012ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T19:48:24Z"
    - latency: 3.455151ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T19:48:24Z"
kind: List
metadata:
  resourceVersion: ""