apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T10:09:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: 35748b9f-7a40-400a-85f7-b20def53a31f
    resourceVersion: "54473"
    uid: 5bc774e1-44e2-442b-9ff6-3d2017675eae
  spec:
    sourcePod: network-check-source-989f8b8dc-sct46
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T10:16:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.053403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 1.144586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 1.229219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 1.483772ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:41:39Z"
    - latency: 880.737µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:40:39Z"
    - latency: 871.988µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:39:39Z"
    - latency: 1.034865ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:38:39Z"
    - latency: 1.180979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:37:39Z"
    - latency: 923.369µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:36:39Z"
    - latency: 1.195873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:35:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T10:09:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: 35748b9f-7a40-400a-85f7-b20def53a31f
    resourceVersion: "55475"
    uid: f61e6a33-4148-4674-ac35-2eb167108cbc
  spec:
    sourcePod: network-check-source-989f8b8dc-sct46
    targetEndpoint: abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T10:15:39Z"
      message: 'load-balancer-api-external: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.573605ms
      message: 'load-balancer-api-external: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:45:39Z"
    - latency: 11.040403ms
      message: 'load-balancer-api-external: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:45:39Z"
    - latency: 4.304711ms
      message: 'load-balancer-api-external: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 7.090352ms
      message: 'load-balancer-api-external: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 5.345042ms
      message: 'load-balancer-api-external: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 6.706961ms
      message: 'load-balancer-api-external: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 4.053225ms
      message: 'load-balancer-api-external: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 6.486022ms
      message: 'load-balancer-api-external: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 7.79117ms
      message: 'load-balancer-api-external: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:41:39Z"
    - latency: 9.265391ms
      message: 'load-balancer-api-external: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T10:09:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: 35748b9f-7a40-400a-85f7-b20def53a31f
    resourceVersion: "55474"
    uid: f4a27a65-ba38-43cf-915a-6fef425cf71d
  spec:
    sourcePod: network-check-source-989f8b8dc-sct46
    targetEndpoint: abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T10:15:39Z"
      message: 'load-balancer-api-internal: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.587384ms
      message: 'load-balancer-api-internal: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:45:39Z"
    - latency: 10.929773ms
      message: 'load-balancer-api-internal: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:45:39Z"
    - latency: 4.285122ms
      message: 'load-balancer-api-internal: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 7.044114ms
      message: 'load-balancer-api-internal: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 5.267258ms
      message: 'load-balancer-api-internal: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 6.682884ms
      message: 'load-balancer-api-internal: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 4.90258ms
      message: 'load-balancer-api-internal: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 6.466389ms
      message: 'load-balancer-api-internal: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 7.793808ms
      message: 'load-balancer-api-internal: tcp connection to abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:41:39Z"
    - latency: 9.245364ms
      message: 'load-balancer-api-internal: resolved host name abd694ebe5c094f79b32364744ce2739-eb4a9eec9b829095.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:41:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T10:09:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-ip-10-0-134-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: 35748b9f-7a40-400a-85f7-b20def53a31f
    resourceVersion: "54471"
    uid: 53d97b81-5619-44d7-998b-717ade66d953
  spec:
    sourcePod: network-check-source-989f8b8dc-sct46
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T10:16:39Z"
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.018599ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 1.948671ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 2.181925ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 2.248537ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:41:39Z"
    - latency: 1.899128ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:40:39Z"
    - latency: 1.916149ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:39:39Z"
    - latency: 2.037581ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:38:39Z"
    - latency: 2.337601ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:37:39Z"
    - latency: 1.918219ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:36:39Z"
    - latency: 2.118667ms
      message: 'network-check-target-ip-10-0-134-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:35:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T10:09:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-ip-10-0-135-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: 35748b9f-7a40-400a-85f7-b20def53a31f
    resourceVersion: "54470"
    uid: aac714eb-4276-4e43-9fa1-98f6aecc9379
  spec:
    sourcePod: network-check-source-989f8b8dc-sct46
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T10:16:39Z"
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 793.006µs
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 1.049497ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 1.436045ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 1.576707ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:41:39Z"
    - latency: 860.643µs
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:40:39Z"
    - latency: 1.318267ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:39:39Z"
    - latency: 927.797µs
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:38:39Z"
    - latency: 1.038322ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:37:39Z"
    - latency: 1.169636ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:36:39Z"
    - latency: 1.056896ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:35:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T10:09:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-ip-10-0-143-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: 35748b9f-7a40-400a-85f7-b20def53a31f
    resourceVersion: "54472"
    uid: 7a409566-68fe-4926-b018-35392e4e8e6f
  spec:
    sourcePod: network-check-source-989f8b8dc-sct46
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T10:16:39Z"
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.245318ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 2.035006ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 2.38518ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 2.295108ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:41:39Z"
    - latency: 2.252522ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:40:39Z"
    - latency: 2.326759ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:39:39Z"
    - latency: 2.134728ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:38:39Z"
    - latency: 2.111556ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:37:39Z"
    - latency: 2.203746ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:36:39Z"
    - latency: 2.267784ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:35:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T10:09:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: 35748b9f-7a40-400a-85f7-b20def53a31f
    resourceVersion: "55473"
    uid: f9e43bc9-a791-480a-a84b-e1e7fcfc3c20
  spec:
    sourcePod: network-check-source-989f8b8dc-sct46
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T10:15:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.959µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:45:39Z"
    - latency: 2.388876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:45:39Z"
    - latency: 1.01324ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 1.753347ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:44:39Z"
    - latency: 959.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 1.924236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:43:39Z"
    - latency: 1.298866ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 1.6557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:42:39Z"
    - latency: 771.227µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T10:41:39Z"
    - latency: 2.324575ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T10:41:39Z"
kind: List
metadata:
  resourceVersion: ""