apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 04923208-2277-4138-a936-ad3440e309f5
    resourceVersion: "56029"
    uid: c580d587-0ae4-4903-81a9-9f474960a720
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vnvp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:41:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.251928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 987.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 887.992µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 1.228964ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:06:06Z"
    - latency: 974.059µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:05:06Z"
    - latency: 901.721µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:04:06Z"
    - latency: 1.012925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:03:06Z"
    - latency: 1.23869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:02:06Z"
    - latency: 1.013636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:01:06Z"
    - latency: 854.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:00:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 04923208-2277-4138-a936-ad3440e309f5
    resourceVersion: "57144"
    uid: 081c9009-18c0-42b8-8fc7-cc78f1000f26
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vnvp
    targetEndpoint: ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:40:06Z"
      message: 'load-balancer-api-external: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.879863ms
      message: 'load-balancer-api-external: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:10:06Z"
    - latency: 8.049306ms
      message: 'load-balancer-api-external: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:10:06Z"
    - latency: 4.49022ms
      message: 'load-balancer-api-external: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 8.850943ms
      message: 'load-balancer-api-external: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 4.787076ms
      message: 'load-balancer-api-external: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 9.068535ms
      message: 'load-balancer-api-external: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 3.185197ms
      message: 'load-balancer-api-external: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 6.486641ms
      message: 'load-balancer-api-external: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 5.275399ms
      message: 'load-balancer-api-external: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:06:06Z"
    - latency: 7.36778ms
      message: 'load-balancer-api-external: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:06:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 04923208-2277-4138-a936-ad3440e309f5
    resourceVersion: "57143"
    uid: 5d1bcef8-cde9-467a-9402-b2ce751d4d01
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vnvp
    targetEndpoint: ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:40:06Z"
      message: 'load-balancer-api-internal: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.615773ms
      message: 'load-balancer-api-internal: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:10:06Z"
    - latency: 8.149479ms
      message: 'load-balancer-api-internal: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:10:06Z"
    - latency: 5.325171ms
      message: 'load-balancer-api-internal: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 8.740417ms
      message: 'load-balancer-api-internal: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 5.272864ms
      message: 'load-balancer-api-internal: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 9.140492ms
      message: 'load-balancer-api-internal: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 3.120959ms
      message: 'load-balancer-api-internal: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 6.518739ms
      message: 'load-balancer-api-internal: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 5.297793ms
      message: 'load-balancer-api-internal: tcp connection to ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:06:06Z"
    - latency: 7.428457ms
      message: 'load-balancer-api-internal: resolved host name ad1b02f90380e47879a32230938e1091-161a69b343be20cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:06:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-130-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 04923208-2277-4138-a936-ad3440e309f5
    resourceVersion: "56025"
    uid: 9238d8c5-5221-4793-a5f7-4e767624b622
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vnvp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:41:06Z"
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.3881ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 1.315021ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 795.88µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 809.921µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:06:06Z"
    - latency: 836.173µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:05:06Z"
    - latency: 1.316514ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:04:06Z"
    - latency: 817.797µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:03:06Z"
    - latency: 1.418008ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:02:06Z"
    - latency: 744.85µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:01:06Z"
    - latency: 1.30846ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:00:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-131-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 04923208-2277-4138-a936-ad3440e309f5
    resourceVersion: "56026"
    uid: 43bae1fa-8371-4aef-901a-540e50bfef29
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vnvp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:41:06Z"
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221235ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 2.091698ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 1.691742ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 2.121921ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:06:06Z"
    - latency: 2.15648ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:05:06Z"
    - latency: 2.152847ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:04:06Z"
    - latency: 2.136429ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:03:06Z"
    - latency: 1.756338ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:02:06Z"
    - latency: 1.926003ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:01:06Z"
    - latency: 2.281242ms
      message: 'network-check-target-ip-10-0-131-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:00:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-137-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 04923208-2277-4138-a936-ad3440e309f5
    resourceVersion: "56027"
    uid: d50b4af4-b40a-4cf8-86b9-ffee651e58b6
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vnvp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:41:06Z"
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.26251ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 2.341263ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 1.603258ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 1.790827ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:06:06Z"
    - latency: 2.150714ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:05:06Z"
    - latency: 1.69882ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:04:06Z"
    - latency: 2.198487ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:03:06Z"
    - latency: 1.498427ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:02:06Z"
    - latency: 2.01613ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:01:06Z"
    - latency: 1.728179ms
      message: 'network-check-target-ip-10-0-137-147: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:00:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T00:34:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 04923208-2277-4138-a936-ad3440e309f5
    resourceVersion: "57141"
    uid: 6cd9a6ed-7736-4ee0-9478-a290352d138d
  spec:
    sourcePod: network-check-source-869dcfcdcd-4vnvp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T00:40:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 746.233µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:10:06Z"
    - latency: 1.763907ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:10:06Z"
    - latency: 935.221µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 1.826875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:09:06Z"
    - latency: 775.851µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 1.639067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:08:06Z"
    - latency: 772.069µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 1.537929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:07:06Z"
    - latency: 865.968µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T01:06:06Z"
    - latency: 1.786949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T01:06:06Z"
kind: List
metadata:
  resourceVersion: ""