apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-124-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-124.ec2.internal
      uid: 4320f591-d314-42a7-9d2f-fa7b7a6cab72
    resourceVersion: "35990"
    uid: 0b12ee23-78f1-4e91-94e3-ce8a163705b8
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk4pl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.055µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:56Z"
    - latency: 1.167263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:56Z"
    - latency: 1.227072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:56Z"
    - latency: 1.33562ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:56Z"
    - latency: 822.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:56Z"
    - latency: 1.11817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:56Z"
    - latency: 1.064381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:56Z"
    - latency: 993.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:56Z"
    - latency: 929.791µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:56Z"
    - latency: 824.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-124-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-124.ec2.internal
      uid: 4320f591-d314-42a7-9d2f-fa7b7a6cab72
    resourceVersion: "39392"
    uid: 92dcc151-990c-411b-925c-d6af68e12a9a
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk4pl
    targetEndpoint: ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:56Z"
      message: 'load-balancer-api-external: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.734647ms
      message: 'load-balancer-api-external: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:33:56Z"
    - latency: 8.754767ms
      message: 'load-balancer-api-external: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:33:56Z"
    - latency: 4.869643ms
      message: 'load-balancer-api-external: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:32:56Z"
    - latency: 8.381096ms
      message: 'load-balancer-api-external: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:32:56Z"
    - latency: 5.964874ms
      message: 'load-balancer-api-external: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:31:56Z"
    - latency: 8.313277ms
      message: 'load-balancer-api-external: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:31:56Z"
    - latency: 4.858285ms
      message: 'load-balancer-api-external: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:30:56Z"
    - latency: 7.767029ms
      message: 'load-balancer-api-external: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:30:56Z"
    - latency: 5.243962ms
      message: 'load-balancer-api-external: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:29:56Z"
    - latency: 7.942731ms
      message: 'load-balancer-api-external: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-124-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-124.ec2.internal
      uid: 4320f591-d314-42a7-9d2f-fa7b7a6cab72
    resourceVersion: "39393"
    uid: 77315466-4633-4620-8b1c-5c240518cc71
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk4pl
    targetEndpoint: ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:56Z"
      message: 'load-balancer-api-internal: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.761353ms
      message: 'load-balancer-api-internal: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:33:56Z"
    - latency: 8.8005ms
      message: 'load-balancer-api-internal: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:33:56Z"
    - latency: 5.392092ms
      message: 'load-balancer-api-internal: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:32:56Z"
    - latency: 8.403435ms
      message: 'load-balancer-api-internal: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:32:56Z"
    - latency: 5.767592ms
      message: 'load-balancer-api-internal: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:31:56Z"
    - latency: 8.380889ms
      message: 'load-balancer-api-internal: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:31:56Z"
    - latency: 4.865121ms
      message: 'load-balancer-api-internal: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:30:56Z"
    - latency: 7.66632ms
      message: 'load-balancer-api-internal: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:30:56Z"
    - latency: 5.266791ms
      message: 'load-balancer-api-internal: tcp connection to ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:29:56Z"
    - latency: 8.019041ms
      message: 'load-balancer-api-internal: resolved host name ab221844574f946759f36012dda9a70e-a74b3d88e1736219.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-124-to-network-check-target-ip-10-0-131-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-124.ec2.internal
      uid: 4320f591-d314-42a7-9d2f-fa7b7a6cab72
    resourceVersion: "35988"
    uid: 28805b37-3b0a-4436-afab-42cf1f490d2c
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk4pl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:56Z"
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.726148ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:56Z"
    - latency: 2.353445ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:56Z"
    - latency: 2.39103ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:56Z"
    - latency: 2.243518ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:56Z"
    - latency: 2.247815ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:56Z"
    - latency: 2.205911ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:56Z"
    - latency: 2.188981ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:56Z"
    - latency: 2.076963ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:56Z"
    - latency: 1.995553ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:56Z"
    - latency: 2.051862ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-124-to-network-check-target-ip-10-0-135-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-124.ec2.internal
      uid: 4320f591-d314-42a7-9d2f-fa7b7a6cab72
    resourceVersion: "35986"
    uid: 500d6d56-66f5-4b39-82ec-211d06205cba
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk4pl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:56Z"
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072184ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:56Z"
    - latency: 909.858µs
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:56Z"
    - latency: 843.013µs
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:56Z"
    - latency: 2.340755ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:56Z"
    - latency: 1.064501ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:56Z"
    - latency: 858.3µs
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:56Z"
    - latency: 837.904µs
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:56Z"
    - latency: 909.012µs
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:56Z"
    - latency: 1.267219ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:56Z"
    - latency: 1.398181ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-124-to-network-check-target-ip-10-0-138-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-124.ec2.internal
      uid: 4320f591-d314-42a7-9d2f-fa7b7a6cab72
    resourceVersion: "35987"
    uid: ca9b75e4-6fcf-4234-95ce-0d6757156541
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk4pl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:52:56Z"
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.763195ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:27:56Z"
    - latency: 1.89293ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:26:56Z"
    - latency: 2.028007ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:25:56Z"
    - latency: 1.698856ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:24:56Z"
    - latency: 1.785175ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:23:56Z"
    - latency: 1.923208ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:22:56Z"
    - latency: 2.0071ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:21:56Z"
    - latency: 2.119946ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:20:56Z"
    - latency: 2.032839ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:19:56Z"
    - latency: 1.897155ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:18:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:45:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-124-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-124.ec2.internal
      uid: 4320f591-d314-42a7-9d2f-fa7b7a6cab72
    resourceVersion: "39391"
    uid: 95541e91-1d63-4851-abd4-868602718100
  spec:
    sourcePod: network-check-source-7cbc45fddc-sk4pl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:51:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.133817ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:33:56Z"
    - latency: 2.131969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:33:56Z"
    - latency: 994.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:32:56Z"
    - latency: 1.973568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:32:56Z"
    - latency: 957.712µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:31:56Z"
    - latency: 1.893227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:31:56Z"
    - latency: 1.064081ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:30:56Z"
    - latency: 2.050269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:30:56Z"
    - latency: 883.974µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T17:29:56Z"
    - latency: 1.793388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T17:29:56Z"
kind: List
metadata:
  resourceVersion: ""