You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

41 lines
1.6 KiB

  1. Network Checker Application
  2. ===========================
  3. With the ``deploy_netchecker`` var enabled (defaults to false), Kargo deploys a
  4. Network Checker Application from the 3rd side `l23network/k8s-netchecker` docker
  5. images. It consists of the server and agents trying to reach the server by usual
  6. for Kubernetes applications network connectivity meanings. Therefore, this
  7. automagically verifies a pod to pod connectivity via the cluster IP and checks
  8. if DNS resolve is functioning as well.
  9. The checks are run by agents on a periodic basis and cover standard and host network
  10. pods as well. The history of performed checks may be found in the agents' application
  11. logs.
  12. To get the most recent and cluster-wide network connectivity report, run from
  13. any of the cluster nodes:
  14. ```
  15. curl http://localhost:31081/api/v1/connectivity_check
  16. ```
  17. Note that Kargo does not invoke the check but only deploys the application, if
  18. requested.
  19. There are related application specifc variables:
  20. ```
  21. netchecker_port: 31081
  22. agent_report_interval: 15
  23. netcheck_namespace: default
  24. agent_img: "quay.io/l23network/k8s-netchecker-agent:v1.0"
  25. server_img: "quay.io/l23network/k8s-netchecker-server:v1.0"
  26. ```
  27. Note that the application verifies DNS resolve for FQDNs comprising only the
  28. combination of the ``netcheck_namespace.dns_domain`` vars, for example the
  29. ``netchecker-service.default.cluster.local``. If you want to deploy the application
  30. to the non default namespace, make sure as well to adjust the ``searchdomains`` var
  31. so the resulting search domain records to contain that namespace, like:
  32. ```
  33. search: foospace.cluster.local default.cluster.local ...
  34. nameserver: ...
  35. ```