apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:57:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-141-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-141.ec2.internal
      uid: d20a1dea-eec6-4c65-b96d-b538216aad0e
    resourceVersion: "58197"
    uid: 32e4650b-4ed6-4d40-8ae0-470519ba3f82
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghql4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:04:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.006622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 794.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 1.222805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 893.861µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:15Z"
    - latency: 972.134µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:15Z"
    - latency: 882.424µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:15Z"
    - latency: 1.244981ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:15Z"
    - latency: 892.657µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:15Z"
    - latency: 959.082µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:15Z"
    - latency: 1.062739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:57:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-141-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-141.ec2.internal
      uid: d20a1dea-eec6-4c65-b96d-b538216aad0e
    resourceVersion: "59127"
    uid: 703a5c3e-2384-4481-9f33-326ad5522f0a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghql4
    targetEndpoint: a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:03:15Z"
      message: 'load-balancer-api-external: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.008604ms
      message: 'load-balancer-api-external: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:33:15Z"
    - latency: 11.238408ms
      message: 'load-balancer-api-external: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:33:15Z"
    - latency: 4.061431ms
      message: 'load-balancer-api-external: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 8.688899ms
      message: 'load-balancer-api-external: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 4.265182ms
      message: 'load-balancer-api-external: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 8.177958ms
      message: 'load-balancer-api-external: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 6.557625ms
      message: 'load-balancer-api-external: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 7.346583ms
      message: 'load-balancer-api-external: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 4.364525ms
      message: 'load-balancer-api-external: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:15Z"
    - latency: 6.364297ms
      message: 'load-balancer-api-external: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:29:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:57:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-141-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-141.ec2.internal
      uid: d20a1dea-eec6-4c65-b96d-b538216aad0e
    resourceVersion: "59126"
    uid: 26ced6b3-6e90-4625-bb98-abc6f8100646
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghql4
    targetEndpoint: a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:03:15Z"
      message: 'load-balancer-api-internal: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.237715ms
      message: 'load-balancer-api-internal: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:33:15Z"
    - latency: 11.1943ms
      message: 'load-balancer-api-internal: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:33:15Z"
    - latency: 3.753995ms
      message: 'load-balancer-api-internal: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 8.727999ms
      message: 'load-balancer-api-internal: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 4.286807ms
      message: 'load-balancer-api-internal: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 8.211305ms
      message: 'load-balancer-api-internal: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 6.302688ms
      message: 'load-balancer-api-internal: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 7.213172ms
      message: 'load-balancer-api-internal: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 6.011198ms
      message: 'load-balancer-api-internal: tcp connection to a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:15Z"
    - latency: 6.307457ms
      message: 'load-balancer-api-internal: resolved host name a95116d1927bd4e2a9bf3a0122c76c94-0fd5384bd087fd77.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:29:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:57:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-141-to-network-check-target-ip-10-0-129-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-141.ec2.internal
      uid: d20a1dea-eec6-4c65-b96d-b538216aad0e
    resourceVersion: "58194"
    uid: 21b72908-653b-41aa-bcaf-25fdcefa5060
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghql4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:04:15Z"
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.422537ms
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 1.31843ms
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 1.329239ms
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 1.14457ms
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:15Z"
    - latency: 931.105µs
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:15Z"
    - latency: 1.081331ms
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:15Z"
    - latency: 1.377152ms
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:15Z"
    - latency: 1.232337ms
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:15Z"
    - latency: 884.112µs
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:15Z"
    - latency: 896.505µs
      message: 'network-check-target-ip-10-0-129-141: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:57:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-141-to-network-check-target-ip-10-0-133-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-141.ec2.internal
      uid: d20a1dea-eec6-4c65-b96d-b538216aad0e
    resourceVersion: "58196"
    uid: b25b6735-ad91-4164-b858-8eb631e449b2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghql4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:04:15Z"
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.272023ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 2.107135ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 2.297739ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 1.874214ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:15Z"
    - latency: 2.718299ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:15Z"
    - latency: 2.020807ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:15Z"
    - latency: 2.599915ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:15Z"
    - latency: 2.274656ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:15Z"
    - latency: 2.376538ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:15Z"
    - latency: 2.462034ms
      message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:57:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-141-to-network-check-target-ip-10-0-143-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-141.ec2.internal
      uid: d20a1dea-eec6-4c65-b96d-b538216aad0e
    resourceVersion: "58195"
    uid: a8a67fcc-f635-47be-a5b7-4a64fc9bf0d9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghql4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:04:15Z"
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.261733ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 2.239695ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 2.374275ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 2.086531ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:15Z"
    - latency: 2.225547ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:28:15Z"
    - latency: 2.033627ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:27:15Z"
    - latency: 2.424037ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:26:15Z"
    - latency: 2.439067ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:25:15Z"
    - latency: 1.982027ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:24:15Z"
    - latency: 2.092227ms
      message: 'network-check-target-ip-10-0-143-37: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T01:57:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-141-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-141.ec2.internal
      uid: d20a1dea-eec6-4c65-b96d-b538216aad0e
    resourceVersion: "59125"
    uid: a16a1b3c-36da-4c30-a232-dfa5097e2444
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ghql4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T02:03:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.995211ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:33:15Z"
    - latency: 2.026294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:33:15Z"
    - latency: 832.159µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 1.775967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:32:15Z"
    - latency: 834.85µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 1.587296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:31:15Z"
    - latency: 1.145217ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 1.811401ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:30:15Z"
    - latency: 1.010345ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T02:29:15Z"
    - latency: 1.706264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T02:29:15Z"
kind: List
metadata:
  resourceVersion: ""