apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-244-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-244.ec2.internal
      uid: 02ea7f5b-f1ae-4de5-bff6-d6cc069e4c16
    resourceVersion: "32370"
    uid: 446b0eeb-0327-44b0-a0ff-a3b37dfbaead
  spec:
    sourcePod: network-check-source-7d88cb55d8-kjsff
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 895.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 870.195µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 1.322505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 1.134376ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 913.422µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:16:28Z"
    - latency: 1.109648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:15:28Z"
    - latency: 1.334663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:14:28Z"
    - 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-07-28T13:13:28Z"
    - latency: 1.057812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:12:28Z"
    - latency: 977.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:11:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-244-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-244.ec2.internal
      uid: 02ea7f5b-f1ae-4de5-bff6-d6cc069e4c16
    resourceVersion: "32371"
    uid: 2277e58b-44e9-4f2c-8e06-a983a7eb8478
  spec:
    sourcePod: network-check-source-7d88cb55d8-kjsff
    targetEndpoint: aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:44:28Z"
      message: 'load-balancer-api-external: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.917898ms
      message: 'load-balancer-api-external: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 7.997842ms
      message: 'load-balancer-api-external: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 5.451804ms
      message: 'load-balancer-api-external: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 8.106881ms
      message: 'load-balancer-api-external: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 5.693277ms
      message: 'load-balancer-api-external: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 7.477574ms
      message: 'load-balancer-api-external: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 5.047602ms
      message: 'load-balancer-api-external: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 9.756216ms
      message: 'load-balancer-api-external: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 5.372637ms
      message: 'load-balancer-api-external: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:16:28Z"
    - latency: 8.003562ms
      message: 'load-balancer-api-external: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:16:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-244-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-244.ec2.internal
      uid: 02ea7f5b-f1ae-4de5-bff6-d6cc069e4c16
    resourceVersion: "32372"
    uid: 9c44a2ff-c3ef-4d3f-8f6d-7d993e09050b
  spec:
    sourcePod: network-check-source-7d88cb55d8-kjsff
    targetEndpoint: aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:44:28Z"
      message: 'load-balancer-api-internal: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.76007ms
      message: 'load-balancer-api-internal: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 8.094324ms
      message: 'load-balancer-api-internal: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 5.412315ms
      message: 'load-balancer-api-internal: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 8.127032ms
      message: 'load-balancer-api-internal: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 5.818473ms
      message: 'load-balancer-api-internal: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 7.543268ms
      message: 'load-balancer-api-internal: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 5.058922ms
      message: 'load-balancer-api-internal: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 9.653398ms
      message: 'load-balancer-api-internal: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 5.344368ms
      message: 'load-balancer-api-internal: tcp connection to aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:16:28Z"
    - latency: 7.937435ms
      message: 'load-balancer-api-internal: resolved host name aaadd35c61ad946448de84e07d429c93-0105c98bdef150ae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:16:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-244-to-network-check-target-ip-10-0-129-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-244.ec2.internal
      uid: 02ea7f5b-f1ae-4de5-bff6-d6cc069e4c16
    resourceVersion: "32366"
    uid: d16ceed3-dfd0-45a0-bdaf-3e22dd468758
  spec:
    sourcePod: network-check-source-7d88cb55d8-kjsff
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:28Z"
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 840.569µs
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 930.405µs
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 811.742µs
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 857.59µs
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 917.658µs
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:16:28Z"
    - latency: 867.677µs
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:15:28Z"
    - latency: 1.19559ms
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:14:28Z"
    - latency: 1.156362ms
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:13:28Z"
    - latency: 1.249937ms
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:12:28Z"
    - latency: 948.88µs
      message: 'network-check-target-ip-10-0-129-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:11:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-244-to-network-check-target-ip-10-0-134-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-244.ec2.internal
      uid: 02ea7f5b-f1ae-4de5-bff6-d6cc069e4c16
    resourceVersion: "32367"
    uid: 692cc6f4-352b-4d2a-94fd-df62f9d0761f
  spec:
    sourcePod: network-check-source-7d88cb55d8-kjsff
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:28Z"
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.111698ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 2.154729ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 2.346194ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 2.477438ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 2.478177ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:16:28Z"
    - latency: 2.392284ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:15:28Z"
    - latency: 2.235464ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:14:28Z"
    - latency: 2.182659ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:13:28Z"
    - latency: 2.445879ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:12:28Z"
    - latency: 2.292431ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:11:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-244-to-network-check-target-ip-10-0-137-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-244.ec2.internal
      uid: 02ea7f5b-f1ae-4de5-bff6-d6cc069e4c16
    resourceVersion: "32368"
    uid: e4330b8e-a3cd-4564-9258-b77b162291ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-kjsff
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:28Z"
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.487394ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 2.396053ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 2.447627ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 2.497705ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 2.474765ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:16:28Z"
    - latency: 2.4919ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:15:28Z"
    - latency: 2.331857ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:14:28Z"
    - latency: 1.992456ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:13:28Z"
    - latency: 2.467974ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:12:28Z"
    - latency: 2.220139ms
      message: 'network-check-target-ip-10-0-137-92: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:11:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-244-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-244.ec2.internal
      uid: 02ea7f5b-f1ae-4de5-bff6-d6cc069e4c16
    resourceVersion: "32369"
    uid: 6b488d59-f1e1-4766-a159-bbd9e0dfa948
  spec:
    sourcePod: network-check-source-7d88cb55d8-kjsff
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:44:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.307µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 1.803415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:20:28Z"
    - latency: 1.131922ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 1.590684ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:19:28Z"
    - latency: 957.361µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 1.720899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:18:28Z"
    - latency: 715.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 1.590599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:17:28Z"
    - latency: 891.167µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:16:28Z"
    - latency: 2.041205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:16:28Z"
kind: List
metadata:
  resourceVersion: ""