apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:47:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-194-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-194.ec2.internal
      uid: b54da257-6200-4219-b9cb-29a36f4a5d2a
    resourceVersion: "152984"
    uid: dc47eb0f-7dd7-40ec-b92f-ce258e53ce03
  spec:
    sourcePod: network-check-source-6f78d59f99-pkpds
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:54:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.082749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:57:43Z"
    - latency: 971.121µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:43Z"
    - latency: 851.386µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:43Z"
    - latency: 1.457054ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:43Z"
    - latency: 1.349361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 918.01µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 802.214µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 986.748µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 1.446091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:43Z"
    - latency: 1.255792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:47:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-194-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-194.ec2.internal
      uid: b54da257-6200-4219-b9cb-29a36f4a5d2a
    resourceVersion: "150208"
    uid: f8b96d58-d644-48a8-80a3-deef2127f42d
  spec:
    sourcePod: network-check-source-6f78d59f99-pkpds
    targetEndpoint: ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:53:43Z"
      message: 'load-balancer-api-external: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.006567ms
      message: 'load-balancer-api-external: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 6.954269ms
      message: 'load-balancer-api-external: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 14.251606ms
      message: 'load-balancer-api-external: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 7.181552ms
      message: 'load-balancer-api-external: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 15.400634ms
      message: 'load-balancer-api-external: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 6.288889ms
      message: 'load-balancer-api-external: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 17.37243ms
      message: 'load-balancer-api-external: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 10.375413ms
      message: 'load-balancer-api-external: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 18.928344ms
      message: 'load-balancer-api-external: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:43Z"
    - latency: 6.927062ms
      message: 'load-balancer-api-external: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:49:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:47:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-194-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-194.ec2.internal
      uid: b54da257-6200-4219-b9cb-29a36f4a5d2a
    resourceVersion: "150207"
    uid: 8cff428a-5732-4819-bf9c-6f0d3cdd91d1
  spec:
    sourcePod: network-check-source-6f78d59f99-pkpds
    targetEndpoint: ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:53:43Z"
      message: 'load-balancer-api-internal: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.745163ms
      message: 'load-balancer-api-internal: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 7.03128ms
      message: 'load-balancer-api-internal: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 15.337183ms
      message: 'load-balancer-api-internal: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 7.282848ms
      message: 'load-balancer-api-internal: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 16.558564ms
      message: 'load-balancer-api-internal: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 6.254382ms
      message: 'load-balancer-api-internal: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 21.928266ms
      message: 'load-balancer-api-internal: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 10.47552ms
      message: 'load-balancer-api-internal: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 18.922478ms
      message: 'load-balancer-api-internal: tcp connection to ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:43Z"
    - latency: 6.993272ms
      message: 'load-balancer-api-internal: resolved host name ac0867472e0ed442abe4b00862c0eea6-30b73cc833100b52.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:49:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:47:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-194-to-network-check-target-ip-10-0-141-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-194.ec2.internal
      uid: b54da257-6200-4219-b9cb-29a36f4a5d2a
    resourceVersion: "152982"
    uid: b0bef4d9-eb84-44f3-9a2d-962436f8ad76
  spec:
    sourcePod: network-check-source-6f78d59f99-pkpds
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:54:43Z"
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.2136ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:57:43Z"
    - latency: 1.836512ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:43Z"
    - latency: 1.916192ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:43Z"
    - latency: 1.91708ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:43Z"
    - latency: 2.032311ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 1.788604ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 1.834316ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 1.848377ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 2.076935ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:43Z"
    - latency: 3.003226ms
      message: 'network-check-target-ip-10-0-141-232: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:47:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-194-to-network-check-target-ip-10-0-142-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-194.ec2.internal
      uid: b54da257-6200-4219-b9cb-29a36f4a5d2a
    resourceVersion: "152981"
    uid: 36fb22b7-b8e3-430f-b5c6-87617940aa01
  spec:
    sourcePod: network-check-source-6f78d59f99-pkpds
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:54:43Z"
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.311688ms
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:57:43Z"
    - latency: 1.036495ms
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:43Z"
    - latency: 1.639216ms
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:43Z"
    - latency: 865.802µs
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:43Z"
    - latency: 1.604124ms
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 962.709µs
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 978.922µs
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 877.494µs
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 1.213033ms
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:43Z"
    - latency: 910.879µs
      message: 'network-check-target-ip-10-0-142-194: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:47:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-194-to-network-check-target-ip-10-0-143-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-194.ec2.internal
      uid: b54da257-6200-4219-b9cb-29a36f4a5d2a
    resourceVersion: "152983"
    uid: d350e777-6cc9-4643-a48c-c86136bb0652
  spec:
    sourcePod: network-check-source-6f78d59f99-pkpds
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:54:43Z"
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.202834ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:57:43Z"
    - latency: 1.977397ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:43Z"
    - latency: 2.271816ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:43Z"
    - latency: 2.456008ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:43Z"
    - latency: 2.368693ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 2.45271ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 1.817145ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 2.080731ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 2.04266ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:43Z"
    - latency: 1.856477ms
      message: 'network-check-target-ip-10-0-143-38: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:47:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-194-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-194.ec2.internal
      uid: b54da257-6200-4219-b9cb-29a36f4a5d2a
    resourceVersion: "150206"
    uid: 48797a10-c7ab-4fdd-bcdb-4ef845dfae47
  spec:
    sourcePod: network-check-source-6f78d59f99-pkpds
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:53:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.137027ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 1.991254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:53:43Z"
    - latency: 1.028088ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 2.031803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:52:43Z"
    - latency: 1.134142ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 1.815471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:51:43Z"
    - latency: 1.027771ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 2.125025ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:50:43Z"
    - latency: 930.427µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:43Z"
    - latency: 2.114114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:49:43Z"
kind: List
metadata:
  resourceVersion: ""