apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:33:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-58.ec2.internal
      uid: 3296a12c-f1a7-48c0-887d-6bacd1986c4e
    resourceVersion: "52851"
    uid: b6cb7f7c-0eda-4264-8ab3-03de84546c83
  spec:
    sourcePod: network-check-source-6f8b768455-l9mr4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:40:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104934ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 1.452853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 1.027751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:30Z"
    - latency: 1.416458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:30Z"
    - latency: 1.200437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:30Z"
    - latency: 910.985µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:30Z"
    - latency: 1.738707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:30Z"
    - latency: 1.083397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:30Z"
    - latency: 985.384µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:30Z"
    - latency: 1.142222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:52:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:33:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-58.ec2.internal
      uid: 3296a12c-f1a7-48c0-887d-6bacd1986c4e
    resourceVersion: "54687"
    uid: 8ddece52-5a2d-43af-99ef-7a3163c9d95e
  spec:
    sourcePod: network-check-source-6f8b768455-l9mr4
    targetEndpoint: a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:39:30Z"
      message: 'load-balancer-api-external: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.493958ms
      message: 'load-balancer-api-external: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:03:30Z"
    - latency: 8.241858ms
      message: 'load-balancer-api-external: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:03:30Z"
    - latency: 5.001584ms
      message: 'load-balancer-api-external: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:30Z"
    - latency: 7.16861ms
      message: 'load-balancer-api-external: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:02:30Z"
    - latency: 4.913532ms
      message: 'load-balancer-api-external: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 7.167614ms
      message: 'load-balancer-api-external: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 3.360652ms
      message: 'load-balancer-api-external: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 7.381961ms
      message: 'load-balancer-api-external: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 5.193253ms
      message: 'load-balancer-api-external: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:30Z"
    - latency: 6.573864ms
      message: 'load-balancer-api-external: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:59:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:33:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-58.ec2.internal
      uid: 3296a12c-f1a7-48c0-887d-6bacd1986c4e
    resourceVersion: "54688"
    uid: c82c34e6-702f-48f4-847a-976e23aa0a3b
  spec:
    sourcePod: network-check-source-6f8b768455-l9mr4
    targetEndpoint: a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:39:30Z"
      message: 'load-balancer-api-internal: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.530305ms
      message: 'load-balancer-api-internal: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:03:30Z"
    - latency: 8.210327ms
      message: 'load-balancer-api-internal: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:03:30Z"
    - latency: 5.018911ms
      message: 'load-balancer-api-internal: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:30Z"
    - latency: 7.176252ms
      message: 'load-balancer-api-internal: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:02:30Z"
    - latency: 3.85365ms
      message: 'load-balancer-api-internal: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 7.13491ms
      message: 'load-balancer-api-internal: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 3.329051ms
      message: 'load-balancer-api-internal: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 7.282562ms
      message: 'load-balancer-api-internal: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 5.202816ms
      message: 'load-balancer-api-internal: tcp connection to a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:30Z"
    - latency: 6.621368ms
      message: 'load-balancer-api-internal: resolved host name a087d6a5ea79342ed826d93a7c7b4f8a-44b6d6d6664f3864.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:59:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:33:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-58-to-network-check-target-ip-10-0-134-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-58.ec2.internal
      uid: 3296a12c-f1a7-48c0-887d-6bacd1986c4e
    resourceVersion: "52850"
    uid: c68e9b4d-e669-4e39-8cbc-c07bdcb8736d
  spec:
    sourcePod: network-check-source-6f8b768455-l9mr4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:40:30Z"
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.565419ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 2.357142ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 2.426633ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:30Z"
    - latency: 2.260308ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:30Z"
    - latency: 2.957607ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:30Z"
    - latency: 2.580556ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:30Z"
    - latency: 2.74631ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:30Z"
    - latency: 2.220183ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:30Z"
    - latency: 2.605397ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:30Z"
    - latency: 2.593692ms
      message: 'network-check-target-ip-10-0-134-196: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:52:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:33:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-58-to-network-check-target-ip-10-0-135-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-58.ec2.internal
      uid: 3296a12c-f1a7-48c0-887d-6bacd1986c4e
    resourceVersion: "52848"
    uid: 2dc0c605-ce49-4656-b8a0-5e640f09500a
  spec:
    sourcePod: network-check-source-6f8b768455-l9mr4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:40:30Z"
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.649654ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 1.009957ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 1.246281ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:30Z"
    - latency: 1.36595ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:30Z"
    - latency: 1.0436ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:30Z"
    - latency: 1.247091ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:30Z"
    - latency: 1.572405ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:30Z"
    - latency: 1.100808ms
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:30Z"
    - latency: 918.668µs
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:30Z"
    - latency: 997.223µs
      message: 'network-check-target-ip-10-0-135-58: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:52:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:33:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-58-to-network-check-target-ip-10-0-140-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-58.ec2.internal
      uid: 3296a12c-f1a7-48c0-887d-6bacd1986c4e
    resourceVersion: "52849"
    uid: 7b9c0b7f-124b-41db-a632-8df5e894f9b8
  spec:
    sourcePod: network-check-source-6f8b768455-l9mr4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:40:30Z"
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.509825ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 1.864154ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 1.977009ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:30Z"
    - latency: 2.268411ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:58:30Z"
    - latency: 2.143606ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:57:30Z"
    - latency: 2.097949ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:56:30Z"
    - latency: 2.277738ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:55:30Z"
    - latency: 2.189361ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:54:30Z"
    - latency: 2.166391ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:53:30Z"
    - latency: 2.058019ms
      message: 'network-check-target-ip-10-0-140-192: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:52:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:33:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-58.ec2.internal
      uid: 3296a12c-f1a7-48c0-887d-6bacd1986c4e
    resourceVersion: "54686"
    uid: 6237b668-3942-4a68-9059-6380e4fe365b
  spec:
    sourcePod: network-check-source-6f8b768455-l9mr4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:39:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127583ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:03:30Z"
    - latency: 1.787242ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:03:30Z"
    - latency: 935.29µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:30Z"
    - latency: 2.101564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:02:30Z"
    - latency: 945.983µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 1.863366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:01:30Z"
    - latency: 1.181729ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 2.024926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:00:30Z"
    - latency: 950.634µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T16:59:30Z"
    - latency: 1.832403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T16:59:30Z"
kind: List
metadata:
  resourceVersion: ""