apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:22:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-163-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-163.ec2.internal
      uid: 16977a1b-eefa-41f2-b5ec-92591acba224
    resourceVersion: "19946"
    uid: b82bcccb-d4f9-4d58-996c-cfbe31edca44
  spec:
    sourcePod: network-check-source-7d88cb55d8-wwph8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:29:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 852.031µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:35Z"
    - latency: 982.321µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:35Z"
    - latency: 894.493µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:35Z"
    - latency: 1.055072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:35Z"
    - latency: 1.240644ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:35Z"
    - latency: 956.366µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:37:35Z"
    - latency: 815.313µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:36:35Z"
    - latency: 893.898µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:35:35Z"
    - latency: 1.093449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:22:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-163-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-163.ec2.internal
      uid: 16977a1b-eefa-41f2-b5ec-92591acba224
    resourceVersion: "21083"
    uid: 86bef342-6a81-4c00-aa1d-eb58a071e371
  spec:
    sourcePod: network-check-source-7d88cb55d8-wwph8
    targetEndpoint: a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:28:35Z"
      message: 'load-balancer-api-external: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.275196ms
      message: 'load-balancer-api-external: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:35Z"
    - latency: 8.279974ms
      message: 'load-balancer-api-external: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:46:35Z"
    - latency: 5.873295ms
      message: 'load-balancer-api-external: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:45:35Z"
    - latency: 6.74074ms
      message: 'load-balancer-api-external: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:45:35Z"
    - latency: 5.958292ms
      message: 'load-balancer-api-external: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:44:35Z"
    - latency: 6.542246ms
      message: 'load-balancer-api-external: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:44:35Z"
    - latency: 5.279323ms
      message: 'load-balancer-api-external: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 7.264386ms
      message: 'load-balancer-api-external: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 6.199094ms
      message: 'load-balancer-api-external: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:35Z"
    - latency: 7.251125ms
      message: 'load-balancer-api-external: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:42:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:22:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-163-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-163.ec2.internal
      uid: 16977a1b-eefa-41f2-b5ec-92591acba224
    resourceVersion: "21082"
    uid: e64bfa11-1e31-4a3f-bff2-06ed0dc8be96
  spec:
    sourcePod: network-check-source-7d88cb55d8-wwph8
    targetEndpoint: a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:28:35Z"
      message: 'load-balancer-api-internal: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.241425ms
      message: 'load-balancer-api-internal: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:35Z"
    - latency: 8.30396ms
      message: 'load-balancer-api-internal: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:46:35Z"
    - latency: 4.936386ms
      message: 'load-balancer-api-internal: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:45:35Z"
    - latency: 6.609332ms
      message: 'load-balancer-api-internal: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:45:35Z"
    - latency: 5.936977ms
      message: 'load-balancer-api-internal: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:44:35Z"
    - latency: 6.43914ms
      message: 'load-balancer-api-internal: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:44:35Z"
    - latency: 5.269245ms
      message: 'load-balancer-api-internal: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 7.280767ms
      message: 'load-balancer-api-internal: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 6.248907ms
      message: 'load-balancer-api-internal: tcp connection to a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:35Z"
    - latency: 7.2823ms
      message: 'load-balancer-api-internal: resolved host name a94d804075c2b45878ea5679009e334f-7b6d6e739d56be3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:42:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:22:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-163-to-network-check-target-ip-10-0-129-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-163.ec2.internal
      uid: 16977a1b-eefa-41f2-b5ec-92591acba224
    resourceVersion: "19945"
    uid: 4ceea038-fd12-4de3-b832-99c544427c06
  spec:
    sourcePod: network-check-source-7d88cb55d8-wwph8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:29:35Z"
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.366235ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 2.429655ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:35Z"
    - latency: 2.366552ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:35Z"
    - latency: 2.173416ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:35Z"
    - latency: 2.235513ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:35Z"
    - latency: 2.040178ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:35Z"
    - latency: 2.079298ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:37:35Z"
    - latency: 1.839939ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:36:35Z"
    - latency: 2.555337ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:35:35Z"
    - latency: 2.211742ms
      message: 'network-check-target-ip-10-0-129-44: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:22:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-163-to-network-check-target-ip-10-0-131-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-163.ec2.internal
      uid: 16977a1b-eefa-41f2-b5ec-92591acba224
    resourceVersion: "19944"
    uid: 4e102909-db0f-4d1a-b098-4b594c13fe25
  spec:
    sourcePod: network-check-source-7d88cb55d8-wwph8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:29:35Z"
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.326787ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 2.478829ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:35Z"
    - latency: 2.118483ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:35Z"
    - latency: 2.337891ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:35Z"
    - latency: 2.270012ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:35Z"
    - latency: 2.404062ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:35Z"
    - latency: 2.920047ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:37:35Z"
    - latency: 2.449277ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:36:35Z"
    - latency: 2.190044ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:35:35Z"
    - latency: 2.260929ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:22:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-163-to-network-check-target-ip-10-0-139-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-163.ec2.internal
      uid: 16977a1b-eefa-41f2-b5ec-92591acba224
    resourceVersion: "19943"
    uid: aa11ac7e-d04f-4836-becb-73b8e7a905fc
  spec:
    sourcePod: network-check-source-7d88cb55d8-wwph8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:29:35Z"
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.310008ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 897.298µs
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:35Z"
    - latency: 971.674µs
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:41:35Z"
    - latency: 940.025µs
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:40:35Z"
    - latency: 949.559µs
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:39:35Z"
    - latency: 1.032701ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:38:35Z"
    - latency: 1.29671ms
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:37:35Z"
    - latency: 839.288µs
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:36:35Z"
    - latency: 939.472µs
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:35:35Z"
    - latency: 945.007µs
      message: 'network-check-target-ip-10-0-139-163: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T08:22:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-163-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-163.ec2.internal
      uid: 16977a1b-eefa-41f2-b5ec-92591acba224
    resourceVersion: "21081"
    uid: 4840f501-59ea-4302-bd63-74fa7490cf9e
  spec:
    sourcePod: network-check-source-7d88cb55d8-wwph8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T08:28:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.432µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:46:35Z"
    - latency: 2.389365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:46:35Z"
    - latency: 813.515µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:45:35Z"
    - latency: 2.073875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:45:35Z"
    - latency: 842.862µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:44:35Z"
    - latency: 1.642048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:44:35Z"
    - latency: 1.131181ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 2.113481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:43:35Z"
    - latency: 742.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T08:42:35Z"
    - latency: 2.094964ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T08:42:35Z"
kind: List
metadata:
  resourceVersion: ""