Let's look at some basic kubectl output options.
Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).
We can start with:
kubectl get no
iperf3 serverwg-quick down wg0/etc/wireguard/wg0.conf file| #!/usr/bin/env bash | |
| NODESAPI=/api/v1/nodes | |
| function getNodes() { | |
| kubectl get --raw $NODESAPI | jq -r '.items[].metadata.name' | |
| } | |
| function getPVCs() { | |
| jq -s '[flatten | .[].pods[].volume[]? | select(has("pvcRef")) | '\ |
| #!/usr/bin/env bash | |
| cd ~/ | |
| mkdir -p ~/.local/bin | |
| wget "https://discordapp.com/api/download/canary?platform=linux&format=tar.gz" -O discord.tar.gz | |
| tar -xvf discord.tar.gz -C ~/.local/bin | |
| sudo ln -s ~/.local/bin/DiscordCanary/discord.png /usr/share/icons/discord.png | |
| sudo ln -s ~/.local/bin/DiscordCanary/DiscordCanary /usr/bin | |
| wget https://gist.githubusercontent.com/AdrianKoshka/a12ca0bfe2f334a9f208aff72f8738c3/raw/9d606ad7ce7cc1dd23f6a99993e2396540538a02/discord.desktop -O discord.desktop | |
| mkdir -p ~/.local/share/applications/ | |
| mv ~/discord.desktop ~/.local/share/applications/ |
| #!/bin/bash | |
| ##################################################### | |
| # Name: Bash CheatSheet for Mac OSX | |
| # | |
| # A little overlook of the Bash basics | |
| # | |
| # Usage: | |
| # | |
| # Author: J. Le Coupanec | |
| # Date: 2014/11/04 |
| MY_BASH_BLUE="\033[0;34m" #Blue | |
| MY_BASH_NOCOLOR="\033[0m" | |
| HISTTIMEFORMAT=`echo -e ${MY_BASH_BLUE}[%F %T] $MY_BASH_NOCOLOR ` | |
| HISTSIZE=20000 | |
| HISTFILESIZE=20000 |
| { | |
| "output": { | |
| "bass_enhancer": { | |
| "amount": 22.0, | |
| "blend": 0.0, | |
| "floor": 10.0, | |
| "floor-active": true, | |
| "harmonics": 9.999999999999995, | |
| "input-gain": 0.0, | |
| "output-gain": -8.0, |
http-tunnel - Tunnel tcp connection through http in Python
sshtunnel - SSH tunnels to remote server
PycURL - Python interface to libcurl
urllib3 - HTTP library with thread-safe connection pooling, file post support, sanity friendly, and more
| Timers provide a great help in troubleshooting network problems. All values are | |
| reported in milliseconds (ms). These timers should be used in conjunction with | |
| the session termination flags. In TCP mode with "option tcplog" set on the | |
| frontend, 3 control points are reported under the form "Tw/Tc/Tt", and in HTTP | |
| mode, 5 control points are reported under the form "TR/Tw/Tc/Tr/Ta". In | |
| addition, three other measures are provided, "Th", "Ti", and "Tq". | |
| Timings events in HTTP mode: | |
| first request 2nd request |