apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-30.ec2.internal
      uid: 55f19052-34e1-4eb1-9bb0-0d8791f21f3c
    resourceVersion: "65173"
    uid: e9a6900e-13c9-42ae-b13f-47496dfcb324
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzfv6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.216682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 1.002601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:54Z"
    - latency: 995.732µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:19:54Z"
    - latency: 880.531µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:18:54Z"
    - latency: 880.32µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:17:54Z"
    - latency: 959.55µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:16:54Z"
    - latency: 994.319µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:15:54Z"
    - latency: 987.972µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:14:54Z"
    - latency: 883.386µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:13:54Z"
    - latency: 1.276814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-30.ec2.internal
      uid: 55f19052-34e1-4eb1-9bb0-0d8791f21f3c
    resourceVersion: "67685"
    uid: 038ad320-217b-4f64-9c15-953a563cfa97
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzfv6
    targetEndpoint: ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:24:54Z"
      message: 'load-balancer-api-external: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.754967ms
      message: 'load-balancer-api-external: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:54Z"
    - latency: 7.624837ms
      message: 'load-balancer-api-external: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:24:54Z"
    - latency: 5.443752ms
      message: 'load-balancer-api-external: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:23:54Z"
    - latency: 7.715847ms
      message: 'load-balancer-api-external: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:23:54Z"
    - latency: 4.967808ms
      message: 'load-balancer-api-external: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:22:54Z"
    - latency: 8.082177ms
      message: 'load-balancer-api-external: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:22:54Z"
    - latency: 4.876224ms
      message: 'load-balancer-api-external: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 7.559176ms
      message: 'load-balancer-api-external: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 4.596934ms
      message: 'load-balancer-api-external: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:54Z"
    - latency: 7.3134ms
      message: 'load-balancer-api-external: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-30.ec2.internal
      uid: 55f19052-34e1-4eb1-9bb0-0d8791f21f3c
    resourceVersion: "67686"
    uid: cc22c211-b518-43bc-b12c-ab69a779163d
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzfv6
    targetEndpoint: ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:24:54Z"
      message: 'load-balancer-api-internal: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.369661ms
      message: 'load-balancer-api-internal: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:54Z"
    - latency: 7.505382ms
      message: 'load-balancer-api-internal: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:24:54Z"
    - latency: 5.426328ms
      message: 'load-balancer-api-internal: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:23:54Z"
    - latency: 7.683475ms
      message: 'load-balancer-api-internal: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:23:54Z"
    - latency: 4.976238ms
      message: 'load-balancer-api-internal: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:22:54Z"
    - latency: 7.982633ms
      message: 'load-balancer-api-internal: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:22:54Z"
    - latency: 3.494227ms
      message: 'load-balancer-api-internal: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 7.584582ms
      message: 'load-balancer-api-internal: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 4.909515ms
      message: 'load-balancer-api-internal: tcp connection to ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:54Z"
    - latency: 7.217968ms
      message: 'load-balancer-api-internal: resolved host name ad06820afe55e4cdaa45c8fa39f92d2a-a9f98b7f542b6f26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:20:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-30-to-network-check-target-ip-10-0-129-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-30.ec2.internal
      uid: 55f19052-34e1-4eb1-9bb0-0d8791f21f3c
    resourceVersion: "65171"
    uid: 8ebbee08-e279-4a03-b374-3eee12ed4fbc
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzfv6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:54Z"
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072746ms
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 906.94µs
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:54Z"
    - latency: 989.224µs
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:19:54Z"
    - latency: 816.814µs
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:18:54Z"
    - latency: 1.006303ms
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:17:54Z"
    - latency: 1.461881ms
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:16:54Z"
    - latency: 1.245956ms
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:15:54Z"
    - latency: 927.868µs
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:14:54Z"
    - latency: 903.443µs
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:13:54Z"
    - latency: 732.654µs
      message: 'network-check-target-ip-10-0-129-30: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-30-to-network-check-target-ip-10-0-138-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-30.ec2.internal
      uid: 55f19052-34e1-4eb1-9bb0-0d8791f21f3c
    resourceVersion: "65170"
    uid: e33ccce1-0600-4aef-907d-3e780786fa9a
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzfv6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:54Z"
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.493009ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 2.382398ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:54Z"
    - latency: 2.415223ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:19:54Z"
    - latency: 2.309346ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:18:54Z"
    - latency: 2.256178ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:17:54Z"
    - latency: 2.311625ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:16:54Z"
    - latency: 2.463516ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:15:54Z"
    - latency: 2.620611ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:14:54Z"
    - latency: 2.168257ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:13:54Z"
    - latency: 2.281227ms
      message: 'network-check-target-ip-10-0-138-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-30-to-network-check-target-ip-10-0-143-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-30.ec2.internal
      uid: 55f19052-34e1-4eb1-9bb0-0d8791f21f3c
    resourceVersion: "65172"
    uid: f99a3869-fd29-4f6e-9e99-f9fb82d9d3f5
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzfv6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:25:54Z"
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.389116ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 2.531287ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:54Z"
    - latency: 2.332322ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:19:54Z"
    - latency: 2.125682ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:18:54Z"
    - latency: 2.11609ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:17:54Z"
    - latency: 2.634958ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:16:54Z"
    - latency: 2.261419ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:15:54Z"
    - latency: 2.306014ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:14:54Z"
    - latency: 2.80413ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:13:54Z"
    - latency: 2.350104ms
      message: 'network-check-target-ip-10-0-143-75: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:12:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:18:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-30.ec2.internal
      uid: 55f19052-34e1-4eb1-9bb0-0d8791f21f3c
    resourceVersion: "67684"
    uid: 00afb3eb-175a-40d1-a138-3ac94a76a93d
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzfv6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:24:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.001µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:54Z"
    - latency: 1.619472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:24:54Z"
    - latency: 992.695µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:23:54Z"
    - latency: 1.652422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:23:54Z"
    - latency: 923.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:22:54Z"
    - latency: 1.582104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:22:54Z"
    - latency: 1.056305ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 2.137407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:21:54Z"
    - latency: 1.205947ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:54Z"
    - latency: 1.715698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:20:54Z"
kind: List
metadata:
  resourceVersion: ""