Zoltán Reegn reegnz

I have created a local Kubernetes cluster with kind. Following are changes you need to get metric-server running on Kind.

Deploy latest metric-server release.

kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.5.0/components.yaml

Within existing arguments to metric-server container, you need to add argument --kubelet-insecure-tls.

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

Don't use VPN services.

No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.

Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.

A Russian translation of this article can be found here, contributed by Timur Demin.
A Turkish translation can be found here, contributed by agyild.
There's also this article about VPN services, which is honestly better written (and has more cat pictures!) than my article.

	#!/bin/bash
	#------------------------------------------------------------------------
	# run-cmd-pod.sh
	#
	# Runs commands in K8s pods when those are not installed there
	# but they're in the worker node.
	#
	# Motivation: You want to run a command in a pod without
	# installing anything in the pod. If that command exists
	# in the worker node running the pod, then you can use

	#!/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")) \| '\

	# If you use bash, this technique isn't really zsh specific. Adapt as needed.
	source ~/keychain-environment-variables.sh

	# AWS configuration example, after doing:
	# $ set-keychain-environment-variable AWS_ACCESS_KEY_ID
	# provide: "AKIAYOURACCESSKEY"
	# $ set-keychain-environment-variable AWS_SECRET_ACCESS_KEY
	# provide: "j1/yoursupersecret/password"
	export AWS_ACCESS_KEY_ID=$(keychain-environment-variable AWS_ACCESS_KEY_ID);
	export AWS_SECRET_ACCESS_KEY=$(keychain-environment-variable AWS_SECRET_ACCESS_KEY);

	<item>
	<name>Use the correct shift keys.</name>
	<identifier>private.correct_shift_keys</identifier>

	<autogen>--KeyToKey-- KeyCode::BACKQUOTE, ModifierFlag::SHIFT_L, KeyCode::VK_NONE</autogen>
	<autogen>--KeyToKey-- KeyCode::1, ModifierFlag::SHIFT_L, KeyCode::VK_NONE</autogen>
	<autogen>--KeyToKey-- KeyCode::2, ModifierFlag::SHIFT_L, KeyCode::VK_NONE</autogen>
	<autogen>--KeyToKey-- KeyCode::3, ModifierFlag::SHIFT_L, KeyCode::VK_NONE</autogen>
	<autogen>--KeyToKey-- KeyCode::4, ModifierFlag::SHIFT_L, KeyCode::VK_NONE</autogen>

	map $http_origin $allow_origin {
	default "";
	"~^https?://(?:[^/]*\.)?(stevebuzonas\.(?:com\|local))(?::[0-9]+)?$" "$http_origin";
	}

	map $request_method $cors_method {
	default "allowed";
	"OPTIONS" "preflight";
	}

	#
	# CORS header support
	#
	# One way to use this is by placing it into a file called "cors_support"
	# under your Nginx configuration directory and placing the following
	# statement inside your location block(s):
	#
	# include cors_support;
	#
	# As of Nginx 1.7.5, add_header supports an "always" parameter which