apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 98d661f7-3695-4aa2-8849-4a3b7a85f6fd
    resourceVersion: "62881"
    uid: 401cde95-02ae-419e-88e1-0f9afe5d2356
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cb5pk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:10:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 946.782µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 1.155712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 1.173071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 1.061463ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 1.124666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:41:28Z"
    - latency: 833.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:40:28Z"
    - latency: 1.089048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:39:28Z"
    - latency: 890.114µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:38:28Z"
    - latency: 871.868µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:37:28Z"
    - latency: 1.609789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:36:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 98d661f7-3695-4aa2-8849-4a3b7a85f6fd
    resourceVersion: "62882"
    uid: d5039429-b4ba-4967-a39d-02c0fa2a3fcb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cb5pk
    targetEndpoint: adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:09:28Z"
      message: 'load-balancer-api-external: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.788068ms
      message: 'load-balancer-api-external: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 8.505663ms
      message: 'load-balancer-api-external: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 3.717118ms
      message: 'load-balancer-api-external: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 9.065117ms
      message: 'load-balancer-api-external: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 4.791487ms
      message: 'load-balancer-api-external: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 10.336921ms
      message: 'load-balancer-api-external: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 4.10323ms
      message: 'load-balancer-api-external: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 12.47713ms
      message: 'load-balancer-api-external: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 4.860353ms
      message: 'load-balancer-api-external: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:41:28Z"
    - latency: 9.086452ms
      message: 'load-balancer-api-external: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:41:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 98d661f7-3695-4aa2-8849-4a3b7a85f6fd
    resourceVersion: "62883"
    uid: 2ea12406-6741-4d59-99e8-62209f1b82c8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cb5pk
    targetEndpoint: adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:09:28Z"
      message: 'load-balancer-api-internal: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.774205ms
      message: 'load-balancer-api-internal: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 8.556497ms
      message: 'load-balancer-api-internal: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 5.068496ms
      message: 'load-balancer-api-internal: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 9.091208ms
      message: 'load-balancer-api-internal: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 5.31619ms
      message: 'load-balancer-api-internal: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 10.372551ms
      message: 'load-balancer-api-internal: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 4.74552ms
      message: 'load-balancer-api-internal: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 12.522407ms
      message: 'load-balancer-api-internal: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 4.419562ms
      message: 'load-balancer-api-internal: tcp connection to adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:41:28Z"
    - latency: 9.122353ms
      message: 'load-balancer-api-internal: resolved host name adb512fe273ba4cf4b3db9f9676ae4a9-88279f2d30431293.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:41:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-136-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 98d661f7-3695-4aa2-8849-4a3b7a85f6fd
    resourceVersion: "62877"
    uid: 054e076f-07cb-4ffe-9de4-18a56eafca42
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cb5pk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:10:28Z"
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120167ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 857.184µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 935.801µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 1.082436ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 1.381602ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:41:28Z"
    - latency: 940.134µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:40:28Z"
    - latency: 829.959µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:39:28Z"
    - latency: 921.534µs
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:38:28Z"
    - latency: 1.411004ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:37:28Z"
    - latency: 1.780932ms
      message: 'network-check-target-ip-10-0-136-17: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:36:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-139-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 98d661f7-3695-4aa2-8849-4a3b7a85f6fd
    resourceVersion: "62878"
    uid: 399d874a-558b-4e4f-93d5-1404adab217d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cb5pk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:10:28Z"
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.146273ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 1.832143ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 1.949137ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 1.988723ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 1.742397ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:41:28Z"
    - latency: 1.903818ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:40:28Z"
    - latency: 1.81609ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:39:28Z"
    - latency: 1.883571ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:38:28Z"
    - latency: 1.947709ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:37:28Z"
    - latency: 1.982338ms
      message: 'network-check-target-ip-10-0-139-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:36:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-ip-10-0-140-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 98d661f7-3695-4aa2-8849-4a3b7a85f6fd
    resourceVersion: "62879"
    uid: 9d10a7ff-6316-49ee-bdb2-0b62e13bed8c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cb5pk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:10:28Z"
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.172156ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 2.457064ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 2.367086ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 2.272108ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 2.212053ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:41:28Z"
    - latency: 1.97418ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:40:28Z"
    - latency: 2.414201ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:39:28Z"
    - latency: 2.051309ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:38:28Z"
    - latency: 2.451726ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:37:28Z"
    - latency: 2.680471ms
      message: 'network-check-target-ip-10-0-140-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:36:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:03:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-17-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-17.ec2.internal
      uid: 98d661f7-3695-4aa2-8849-4a3b7a85f6fd
    resourceVersion: "62880"
    uid: c40d27f0-b56c-49e7-82ff-9e4af72b285e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cb5pk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:09:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 748.975µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 2.076254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:45:28Z"
    - latency: 1.043021ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 1.974534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:44:28Z"
    - latency: 1.051055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 1.763004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:43:28Z"
    - latency: 1.092224ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 1.742991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:42:28Z"
    - latency: 878.23µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:41:28Z"
    - latency: 1.585154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:41:28Z"
kind: List
metadata:
  resourceVersion: ""