Satria Sahputra satriashp

Kubectl output options

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

Setup Kubernetes Cluster on AWS

Installing kops

Prerequisite

kubectl is required, see here.

Linux

curl -LO https://github.com/kubernetes/kops/releases/download/$(curl -s https://api.github.com/repos/kubernetes/kops/releases/latest | grep tag_name | cut -d '"' -f 4)/kops-linux-amd64
chmod +x kops-linux-amd64
sudo mv kops-linux-amd64 /usr/local/bin/kops

psql: FATAL: Peer authentication failed for user “postgres” (or any user)

The connection failed because by default psql connects over UNIX sockets using peer authentication, that requires the current UNIX user to have the same user name as psql. So you will have to create the UNIX user postgres and then login as postgres or use sudo -u postgres psql database-name for accessing the database (and psql should not ask for a password).

If you cannot or do not want to create the UNIX user, like if you just want to connect to your database for ad hoc queries, forcing a socket connection using psql --host=localhost --dbname=database-name --username=postgres (as pointed out by @meyerson answer) will solve your immediate problem.

But if you intend to force password authentication over Unix sockets instead of the peer method, try changing the following pg_hba.conf* line:

from

Prerequisites

Install Docker Engine - Community.
Install Docker Compose.

Installation

Make home directory for printerous projects and clone printerous repo in it.

For example:

── printerous

	# Sample Nginx config with sane caching settings for modern web development
	#
	# Motivation:
	# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
	# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
	# and juicy version of your assets available.
	# At some point, however, you want to show your work to testers, your boss or your client.
	# After you implemented and deployed their feedback, they reload the testing page – and report
	# the exact same issues as before! What happened? Of course, they did not have developer tools
	# open, and of course, they did not empty their caches before navigating to your site.

	-- Create a group
	CREATE ROLE readaccess;

	-- Grant access to existing tables
	GRANT USAGE ON SCHEMA public TO readaccess;
	GRANT SELECT ON ALL TABLES IN SCHEMA public TO readaccess;

	-- Grant access to future tables
	ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO readaccess;

	# install helm

	curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get \| bash

	kubectl create serviceaccount -n kube-system tiller
	kubectl create clusterrolebinding tiller-binding --clusterrole=cluster-admin --serviceaccount kube-system:tiller

	# run tiller with specific tiller account
	helm init --service-account tiller

	Backup:
	docker exec -t -u postgres your-db-container pg_dumpall -c > dump_`date +%d-%m-%Y"_"%H_%M_%S`.sql

	Restore:
	cat your_dump.sql \| docker exec -i your-db-container psql -Upostgres

	Backup:
	docker exec -t -u postgres your-db-container pg_dumpall -c > dump_`date +%d-%m-%Y"_"%H_%M_%S`.sql

	Restore:
	cat your_dump.sql \| docker exec -i your-db-container psql -Upostgres

	# Backup
	docker exec CONTAINER /usr/bin/mysqldump -u root --password=root DATABASE > backup.sql

	# Restore
	cat backup.sql \| docker exec -i CONTAINER /usr/bin/mysql -u root --password=root DATABASE