apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:43:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-223.ec2.internal
      uid: e6f18ebe-1d65-43fe-a5b4-2f953df20203
    resourceVersion: "67608"
    uid: 4a8faab7-8a74-44ba-a721-5c87b646e7e1
  spec:
    sourcePod: network-check-source-6f8b768455-9pdfn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:50:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.734µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 1.009448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 1.046034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 1.46921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:15:25Z"
    - latency: 926.373µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:14:25Z"
    - latency: 1.125688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:13:25Z"
    - latency: 1.755795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:12:25Z"
    - latency: 1.027474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:11:25Z"
    - latency: 1.422632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:10:25Z"
    - latency: 1.130938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:09:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:43:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-223.ec2.internal
      uid: e6f18ebe-1d65-43fe-a5b4-2f953df20203
    resourceVersion: "68593"
    uid: 1831cc2d-2bb2-432f-bf8d-cf1f831ca031
  spec:
    sourcePod: network-check-source-6f8b768455-9pdfn
    targetEndpoint: a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:49:25Z"
      message: 'load-balancer-api-external: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.36379ms
      message: 'load-balancer-api-external: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:19:25Z"
    - latency: 10.575701ms
      message: 'load-balancer-api-external: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:19:25Z"
    - latency: 6.139516ms
      message: 'load-balancer-api-external: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 8.916747ms
      message: 'load-balancer-api-external: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 3.663849ms
      message: 'load-balancer-api-external: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 8.690525ms
      message: 'load-balancer-api-external: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 5.34395ms
      message: 'load-balancer-api-external: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 8.715968ms
      message: 'load-balancer-api-external: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 5.52487ms
      message: 'load-balancer-api-external: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:15:25Z"
    - latency: 12.356425ms
      message: 'load-balancer-api-external: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:15:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:43:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-223.ec2.internal
      uid: e6f18ebe-1d65-43fe-a5b4-2f953df20203
    resourceVersion: "68594"
    uid: e3875fe1-c8ad-4cb6-b0af-3799aa7ac816
  spec:
    sourcePod: network-check-source-6f8b768455-9pdfn
    targetEndpoint: a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:49:25Z"
      message: 'load-balancer-api-internal: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.202962ms
      message: 'load-balancer-api-internal: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:19:25Z"
    - latency: 10.532043ms
      message: 'load-balancer-api-internal: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:19:25Z"
    - latency: 6.126689ms
      message: 'load-balancer-api-internal: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 8.929422ms
      message: 'load-balancer-api-internal: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 3.598942ms
      message: 'load-balancer-api-internal: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 8.650621ms
      message: 'load-balancer-api-internal: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 5.345934ms
      message: 'load-balancer-api-internal: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 8.68306ms
      message: 'load-balancer-api-internal: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 5.493122ms
      message: 'load-balancer-api-internal: tcp connection to a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:15:25Z"
    - latency: 12.36ms
      message: 'load-balancer-api-internal: resolved host name a27f47f57d66346baa6b0d073f217920-2ce95bbe5da1a5a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:15:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:43:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-223-to-network-check-target-ip-10-0-128-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-223.ec2.internal
      uid: e6f18ebe-1d65-43fe-a5b4-2f953df20203
    resourceVersion: "67605"
    uid: 0cb7f34f-4fff-44f9-932d-c03f1d03e8d7
  spec:
    sourcePod: network-check-source-6f8b768455-9pdfn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:50:25Z"
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.576µs
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 1.021676ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 944.542µs
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 1.759459ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:15:25Z"
    - latency: 969.529µs
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:14:25Z"
    - latency: 2.114825ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:13:25Z"
    - latency: 2.469101ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:12:25Z"
    - latency: 1.92802ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:11:25Z"
    - latency: 1.009444ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:10:25Z"
    - latency: 2.207131ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:09:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:43:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-223-to-network-check-target-ip-10-0-133-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-223.ec2.internal
      uid: e6f18ebe-1d65-43fe-a5b4-2f953df20203
    resourceVersion: "67606"
    uid: 99f0512e-e71b-4b51-b067-5e8a1a2eb5d3
  spec:
    sourcePod: network-check-source-6f8b768455-9pdfn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:50:25Z"
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.131344ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 2.037934ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 2.362957ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 2.387116ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:15:25Z"
    - latency: 2.115891ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:14:25Z"
    - latency: 2.292723ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:13:25Z"
    - latency: 2.913705ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:12:25Z"
    - latency: 2.942219ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:11:25Z"
    - latency: 2.809574ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:10:25Z"
    - latency: 2.386431ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:09:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:43:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-223-to-network-check-target-ip-10-0-135-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-223.ec2.internal
      uid: e6f18ebe-1d65-43fe-a5b4-2f953df20203
    resourceVersion: "67607"
    uid: 4e77f9d0-d24f-48af-8a91-9145f744f132
  spec:
    sourcePod: network-check-source-6f8b768455-9pdfn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:50:25Z"
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.036594ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 2.449858ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 2.350413ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 2.569378ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:15:25Z"
    - latency: 2.603728ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:14:25Z"
    - latency: 2.847528ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:13:25Z"
    - latency: 2.553634ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:12:25Z"
    - latency: 2.909994ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:11:25Z"
    - latency: 2.435305ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:10:25Z"
    - latency: 2.735708ms
      message: 'network-check-target-ip-10-0-135-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:09:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:43:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-223.ec2.internal
      uid: e6f18ebe-1d65-43fe-a5b4-2f953df20203
    resourceVersion: "68592"
    uid: 13015efb-3fc6-41c3-8e2e-86d60dfdd33b
  spec:
    sourcePod: network-check-source-6f8b768455-9pdfn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:49:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.106186ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:19:25Z"
    - latency: 2.315398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:19:25Z"
    - latency: 799.821µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 2.336962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:18:25Z"
    - latency: 926.541µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 1.845805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:17:25Z"
    - latency: 1.031344ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 2.402531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:16:25Z"
    - latency: 1.111223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:15:25Z"
    - latency: 2.526118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:15:25Z"
kind: List
metadata:
  resourceVersion: ""