Skip to content

Instantly share code, notes, and snippets.

Adrian Goins oskapt

Block or report user

Report or block oskapt

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

Hello! This gist goes with this video, which covers shortcuts and strategies for working with the K8s command line. You can see all of my videos on YouTube at


I use Fish as my shell, but I know that a lot of people are using Bash. Here are two ways to concatenate config files for kubectl into the KUBECONFIG environment variable. If you're using zsh or tcsh you'll know how to convert these to your shell's format.

You can call these from your shell init file, or if you want to temporarily disable a script, append .bak or .disabled to its extension and run the script manually.

You can even hotkey it on something like the Elgato Stream Deck.

oskapt /
Created Aug 2, 2019 — forked from superseb/
Restore Rancher 2 cluster/node agents on clusters

Restore Rancher 2 cluster/node agents on clusters

This is an unsupported scenario, see when there is an official solution.

When cattle-cluster-agent and/or cattle-node-agent are accidentally deleted, or when server-url/cacerts are changed.

Generate definitions

  • Generate API token in the UI (user -> API & Keys) and save the Bearer token
  • Find the clusterid in the Rancher UI (format is c-xxxxx), its in the address bar when the cluster is selected
oskapt /
Created Aug 2, 2019 — forked from superseb/
Generate Rancher 2 cluster/node agent definitions

Generate Rancher 2 cluster/node agents definitions

This is not official documentation/tooling, use with caution

This generate the Kubernetes definitions of the cattle-cluster-agent Deployment and cattle-node-agent DaemonSet, in case it's accidentally removed/server-url was changed/certficates were changed. It is supposed to run on every cluster Rancher manages. If you have custom clusters created in Rancher, see Kubeconfig for Custom clusters created in Rancher how to obtain the kubeconfig to directly talk to the Kubernetes API (as usually it doesn't work via Rancher anymore). For other clusters, use the tools provided by the provider to get the kubeconfig.

IMPORTANT: You get the cluster/node agents definitions from Rancher, and you apply them to the cluster that is created/managed so you need to switch kubeconfig to point to that cluster before applying them.

Running it

oskapt / ip-ranges.txt
Created May 12, 2019 — forked from PSJoshi/ip-ranges.txt
IP ranges for Google, Amazon etc
View ip-ranges.txt
* CloudFare IP list:
* Google's IP addresses:
nslookup -q=TXT
nslookup -q=TXT
nslookup -q=TXT
Each of the above line will display a CIDR block or Google’s IP addresses.
* Amazon IP addresses:
# Based on, thanks!
function cali_interface_for_container() {
container_name=$(docker inspect --format='{{.Name}}' "${1}")
# Get the process ID for the container named ${1}:
local pid=$(docker inspect -f '{{.State.Pid}}' "${1}")

Keybase proof

I hereby claim:

  • I am oskapt on github.
  • I am oskapt ( on keybase.
  • I have a public key ASAIGf3Y3vD9scPLvNC7Z-yOKyU_AvKCaMoHQwJjWmaEmwo

To claim this, I am signing this object:

oskapt / rc.netdata
Created Jun 24, 2018
Netdata init script for Synology DSM
View rc.netdata
# Install this as `/etc/rc.netdata` and call it from `/etc/rc.local`
# to have it executed on boot.
TIMEOUT=30 # seconds to wait for netdata to exit
[ -x $DAEMON ] || exit 0
You can’t perform that action at this time.