The curl command line tool has a reporting option which you can use to measure different bits of timing in the network handling. This can be useful to monitor or investigate network issues: Example output: You can also insert \n’s in the option to put the result on multiple lines:
Github Project: https://github.com/atkaper/k8s-check-certificate-chains Ingress/nginx (running in Kubernetes / K8S) does not like silly certificates, therefore I created two scripts to find wrong ones. The script get-all-k8s-certificates.sh retrieves all certificates from kubernetes, and the check-certificate-chains.sh script verifies the chain’s are complete and in proper ordering. Added md5 hash check on crt and key file to verify the two belong to each other. The check-certificate-chains.sh just reports on WRONG certificates. Run with “-v” option to also show OK’s. Thijs.
Github Project: https://github.com/atkaper/simple-tcp-vpn-over-ssh-socks Poor-man’s VPN for TCP traffic over SSH dynamic socks tunnel, uses Linux/iptables Taken some TCP tunneling code from Christophe Devine, and turned it into a transparent socks proxy. This serves as a lightweight / poor-man’s VPN connection, to combine firewalled networks into one. Requirements; use linux on your end, and you need to be able to connect to an SSH server on the network you want to reach. And the local and remote network IP-ranges should NOT…
Github Project: https://github.com/atkaper/k8s-network-test-daemonset Description An on-premise K8S (kubernetes) cluster needs a proper working virtual network to connect all masters and nodes to each other. In our situation, the host machines (vmware redhat), are not all 100% the same, and can not easily be wiped clean on new K8S and OS upgrades. Therefor we sometimes experienced issues in which the nodes or masters could not always reach each other. We did use the flannel network, which often caused weird issues. We…