apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:03:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 5809a7c9-ea86-4d41-98df-d6098b5df984
    resourceVersion: "59751"
    uid: 0e14553a-9988-4796-9d74-f4774c254925
  spec:
    sourcePod: network-check-source-7cbc45fddc-kz5np
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:10:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 1.172087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 1.781711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:17Z"
    - latency: 954.017µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:17Z"
    - latency: 1.621579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:17Z"
    - latency: 1.477742ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:17Z"
    - latency: 1.306946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:17Z"
    - latency: 1.52053ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:17Z"
    - latency: 1.271998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:17Z"
    - latency: 1.34061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:03:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 5809a7c9-ea86-4d41-98df-d6098b5df984
    resourceVersion: "62095"
    uid: bdfd6b2b-65f3-427b-a2a1-04f3ab50ff21
  spec:
    sourcePod: network-check-source-7cbc45fddc-kz5np
    targetEndpoint: aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:09:18Z"
      message: 'load-balancer-api-external: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.898488ms
      message: 'load-balancer-api-external: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:33:17Z"
    - latency: 8.424048ms
      message: 'load-balancer-api-external: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:33:17Z"
    - latency: 5.704383ms
      message: 'load-balancer-api-external: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:32:17Z"
    - latency: 6.67638ms
      message: 'load-balancer-api-external: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:32:17Z"
    - latency: 4.984473ms
      message: 'load-balancer-api-external: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 7.951406ms
      message: 'load-balancer-api-external: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 4.024868ms
      message: 'load-balancer-api-external: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 7.464154ms
      message: 'load-balancer-api-external: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 5.724517ms
      message: 'load-balancer-api-external: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:17Z"
    - latency: 6.751119ms
      message: 'load-balancer-api-external: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:29:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:03:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 5809a7c9-ea86-4d41-98df-d6098b5df984
    resourceVersion: "62094"
    uid: 7f8667b6-304c-4401-a0be-de804b7f7998
  spec:
    sourcePod: network-check-source-7cbc45fddc-kz5np
    targetEndpoint: aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:09:18Z"
      message: 'load-balancer-api-internal: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.883783ms
      message: 'load-balancer-api-internal: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:33:17Z"
    - latency: 8.300117ms
      message: 'load-balancer-api-internal: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:33:17Z"
    - latency: 4.608352ms
      message: 'load-balancer-api-internal: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:32:17Z"
    - latency: 6.642787ms
      message: 'load-balancer-api-internal: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:32:17Z"
    - latency: 4.994857ms
      message: 'load-balancer-api-internal: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 7.839541ms
      message: 'load-balancer-api-internal: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 4.372645ms
      message: 'load-balancer-api-internal: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 7.446627ms
      message: 'load-balancer-api-internal: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 5.719097ms
      message: 'load-balancer-api-internal: tcp connection to aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:17Z"
    - latency: 6.701762ms
      message: 'load-balancer-api-internal: resolved host name aea7b5fd562464ce0a72c4eb199c2370-f4e1f48c00b737a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:29:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:03:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-129-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 5809a7c9-ea86-4d41-98df-d6098b5df984
    resourceVersion: "59749"
    uid: 864aa535-2bd9-4769-ae7c-e00a3981220c
  spec:
    sourcePod: network-check-source-7cbc45fddc-kz5np
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:10:17Z"
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.08968ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 2.140794ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 2.350698ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:17Z"
    - latency: 2.001293ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:17Z"
    - latency: 2.208226ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:17Z"
    - latency: 2.388362ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:17Z"
    - latency: 2.621576ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:17Z"
    - latency: 2.351466ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:17Z"
    - latency: 2.088163ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:17Z"
    - latency: 2.388071ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:03:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-135-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 5809a7c9-ea86-4d41-98df-d6098b5df984
    resourceVersion: "59748"
    uid: 85ecd240-9ad7-4f4f-942c-99a56aedc3b1
  spec:
    sourcePod: network-check-source-7cbc45fddc-kz5np
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:10:17Z"
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.559837ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 997.304µs
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 1.318886ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:17Z"
    - latency: 1.061968ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:17Z"
    - latency: 1.140236ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:17Z"
    - latency: 1.779647ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:17Z"
    - latency: 996.886µs
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:17Z"
    - latency: 1.329344ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:17Z"
    - latency: 1.215139ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:17Z"
    - latency: 1.048184ms
      message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:03:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-136-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 5809a7c9-ea86-4d41-98df-d6098b5df984
    resourceVersion: "59750"
    uid: a5ee6338-cb95-4e32-8f19-b187c219c6bd
  spec:
    sourcePod: network-check-source-7cbc45fddc-kz5np
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:10:17Z"
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.196763ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 2.332699ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 2.24745ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:17Z"
    - latency: 1.959613ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:28:17Z"
    - latency: 2.301725ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:27:17Z"
    - latency: 2.453935ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:26:17Z"
    - latency: 2.562688ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:25:17Z"
    - latency: 2.414872ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:24:17Z"
    - latency: 1.963679ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:23:17Z"
    - latency: 2.262876ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:22:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T18:03:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-209-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-209.ec2.internal
      uid: 5809a7c9-ea86-4d41-98df-d6098b5df984
    resourceVersion: "62093"
    uid: e3cdac4f-7045-4fdc-834c-840eb381c012
  spec:
    sourcePod: network-check-source-7cbc45fddc-kz5np
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T18:09:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.133074ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:33:17Z"
    - latency: 2.010291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:33:17Z"
    - latency: 1.151754ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:32:17Z"
    - latency: 2.005467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:32:17Z"
    - latency: 1.108749ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 1.718971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:31:17Z"
    - latency: 1.186311ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 2.19535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:30:17Z"
    - latency: 1.052072ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T18:29:17Z"
    - latency: 2.157198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T18:29:17Z"
kind: List
metadata:
  resourceVersion: ""