apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-89-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-89.ec2.internal
      uid: c6ef0c6c-e29d-4734-9cc0-af17dfb2a9aa
    resourceVersion: "70350"
    uid: 88430a41-fb65-4726-ba0c-2d48f65e11b0
  spec:
    sourcePod: network-check-source-7d88cb55d8-ckhct
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.42µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:09Z"
    - latency: 1.603892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:09Z"
    - latency: 1.076211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:09Z"
    - latency: 1.20475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:09Z"
    - latency: 1.020931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:09Z"
    - latency: 945.322µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:09Z"
    - latency: 954.424µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:09Z"
    - latency: 1.292706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:09Z"
    - latency: 1.266881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:09Z"
    - latency: 1.012123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-89-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-89.ec2.internal
      uid: c6ef0c6c-e29d-4734-9cc0-af17dfb2a9aa
    resourceVersion: "84093"
    uid: 24ad87b3-29cb-410c-9a5e-c53f3982d3a4
  spec:
    sourcePod: network-check-source-7d88cb55d8-ckhct
    targetEndpoint: a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:50:09Z"
      message: 'load-balancer-api-external: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.067801ms
      message: 'load-balancer-api-external: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:32:09Z"
    - latency: 6.784651ms
      message: 'load-balancer-api-external: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:32:09Z"
    - latency: 4.860057ms
      message: 'load-balancer-api-external: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:31:09Z"
    - latency: 8.196205ms
      message: 'load-balancer-api-external: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:31:09Z"
    - latency: 5.906558ms
      message: 'load-balancer-api-external: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:30:09Z"
    - latency: 15.146594ms
      message: 'load-balancer-api-external: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:30:09Z"
    - latency: 4.3778ms
      message: 'load-balancer-api-external: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:29:09Z"
    - latency: 7.134755ms
      message: 'load-balancer-api-external: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:29:09Z"
    - latency: 4.157839ms
      message: 'load-balancer-api-external: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:09Z"
    - latency: 7.82397ms
      message: 'load-balancer-api-external: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:28:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-89-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-89.ec2.internal
      uid: c6ef0c6c-e29d-4734-9cc0-af17dfb2a9aa
    resourceVersion: "84092"
    uid: d4887b8c-0ab6-43e7-b904-bfd6bbd972fd
  spec:
    sourcePod: network-check-source-7d88cb55d8-ckhct
    targetEndpoint: a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:50:09Z"
      message: 'load-balancer-api-internal: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.079275ms
      message: 'load-balancer-api-internal: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:32:09Z"
    - latency: 6.743324ms
      message: 'load-balancer-api-internal: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:32:09Z"
    - latency: 4.891319ms
      message: 'load-balancer-api-internal: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:31:09Z"
    - latency: 8.224879ms
      message: 'load-balancer-api-internal: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:31:09Z"
    - latency: 6.01149ms
      message: 'load-balancer-api-internal: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:30:09Z"
    - latency: 15.094585ms
      message: 'load-balancer-api-internal: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:30:09Z"
    - latency: 4.400516ms
      message: 'load-balancer-api-internal: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:29:09Z"
    - latency: 7.256868ms
      message: 'load-balancer-api-internal: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:29:09Z"
    - latency: 4.48978ms
      message: 'load-balancer-api-internal: tcp connection to a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:09Z"
    - latency: 7.776854ms
      message: 'load-balancer-api-internal: resolved host name a6d17ae440f6e4627ab27c1e0bdd0f36-8eb7ae0490379579.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:28:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-89-to-network-check-target-ip-10-0-136-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-89.ec2.internal
      uid: c6ef0c6c-e29d-4734-9cc0-af17dfb2a9aa
    resourceVersion: "70346"
    uid: cd5d012c-98a3-4862-96e5-ad5e26b6ddda
  spec:
    sourcePod: network-check-source-7d88cb55d8-ckhct
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:09Z"
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.561µs
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:09Z"
    - latency: 842.407µs
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:09Z"
    - latency: 900.643µs
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:09Z"
    - latency: 1.005585ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:09Z"
    - latency: 911.461µs
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:09Z"
    - latency: 1.096941ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:09Z"
    - latency: 1.754605ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:09Z"
    - latency: 1.128082ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:09Z"
    - latency: 1.219881ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:09Z"
    - latency: 1.753244ms
      message: 'network-check-target-ip-10-0-136-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-89-to-network-check-target-ip-10-0-137-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-89.ec2.internal
      uid: c6ef0c6c-e29d-4734-9cc0-af17dfb2a9aa
    resourceVersion: "70349"
    uid: e535255e-8590-4c00-aa7c-9088d2908728
  spec:
    sourcePod: network-check-source-7d88cb55d8-ckhct
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:09Z"
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.063706ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:09Z"
    - latency: 2.123421ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:09Z"
    - latency: 1.989443ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:09Z"
    - latency: 2.320254ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:09Z"
    - latency: 2.366187ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:09Z"
    - latency: 2.225438ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:09Z"
    - latency: 2.218793ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:09Z"
    - latency: 2.592059ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:09Z"
    - latency: 2.302605ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:09Z"
    - latency: 2.325135ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-89-to-network-check-target-ip-10-0-142-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-89.ec2.internal
      uid: c6ef0c6c-e29d-4734-9cc0-af17dfb2a9aa
    resourceVersion: "70347"
    uid: 4c54b61d-2cde-4100-8b3b-64eb66c05a72
  spec:
    sourcePod: network-check-source-7d88cb55d8-ckhct
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:51:09Z"
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.140953ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:26:09Z"
    - latency: 2.116188ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:25:09Z"
    - latency: 2.156431ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:24:09Z"
    - latency: 2.250855ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:23:09Z"
    - latency: 2.114108ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:22:09Z"
    - latency: 2.14331ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:21:09Z"
    - latency: 2.520773ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:20:09Z"
    - latency: 2.419072ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:19:09Z"
    - latency: 2.301999ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:18:09Z"
    - latency: 2.403141ms
      message: 'network-check-target-ip-10-0-142-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:17:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T17:44:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-89-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-89.ec2.internal
      uid: c6ef0c6c-e29d-4734-9cc0-af17dfb2a9aa
    resourceVersion: "84091"
    uid: e68c09f5-c013-4647-a11f-65223b00c436
  spec:
    sourcePod: network-check-source-7d88cb55d8-ckhct
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T17:50:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.154248ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:32:09Z"
    - latency: 1.932635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:32:09Z"
    - latency: 1.061534ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:31:09Z"
    - latency: 1.974383ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:31:09Z"
    - latency: 1.015046ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:30:09Z"
    - latency: 2.075608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:30:09Z"
    - latency: 1.113721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:29:09Z"
    - latency: 2.031566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:29:09Z"
    - latency: 1.08414ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T18:28:09Z"
    - latency: 2.46278ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T18:28:09Z"
kind: List
metadata:
  resourceVersion: ""