Karan Sharma mr-karan

EKS uses a custom authenticator tool called "aws-iam-authenticator". The basic idea is to make the auth flow in EKS easier by using the tools you already use in AWS.

To wrap your head around the flow, consider three separate entities:

A kubernetes resource (entire namespace, specific pods/configs etc)
An action (get, watch, list, create, delete etc)
An IAM role/user created on AWS

This is a simple docker-compose file. It creates 2 running instances of image (containers) from redis and postgres. Exposes port 9379 for redis and port 9432 for postgres on your local machine

I created a network called backend. You can check ip addr and see the newly created network. The way it works is that, both containers will be on same network bridge. Think of it like a VLAN? network basically does a lot of things behind the scenes, but most importantly it lets you access the other container through the service name defined in docker-compose file. From your redis, if you want to access postgres 5432 port, you can do using db:5432. So host is not localhost it is db. db internally resolves to the private ip of the network interface you saw in ip addr when you created backend network. docker has created an entry in /etc/resolv.conf which is 127.0.0.11. It is an internal dns namesever running in your docker daemon, which resolves all the containers' service name to their privat

Orderbook

Bid	Ask

'''
Sample comment
'''

var x=4;

	thread 'vector-worker' panicked at 'Tried to ack beyond read offset', /project/lib/vector-core/buffers/src/disk/leveldb_buffer/reader.rs:184:13
	note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
	thread 'vector-worker' panicked at 'Tried to ack beyond read offset', /project/lib/vector-core/buffers/src/disk/leveldb_buffer/reader.rs:184:13
	stack backtrace:
	thread 'vector-worker' panicked at 'Tried to ack beyond read offset', /project/lib/vector-core/buffers/src/disk/leveldb_buffer/reader.rs:184:13
	thread 'vector-worker' panicked at 'Tried to ack beyond read offset', /project/lib/vector-core/buffers/src/disk/leveldb_buffer/reader.rs:184:13
	0: 0x55df1f0de430 - std::backtrace_rs::backtrace::libunwind::trace::h34055254b57d8e79
	at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/std/src/../../backtrace/src/backtrace/libunwind.rs:90:5
	1: 0x55df1f0de430 - std::backtrace_rs::backtrace::trace_unsynchronized::h8f1e3fbd9afff6ec

	# coding: utf-8
	import csv
	import os

	from itertools import tee, islice


	LINES_SPLIT = 1000

	def chunks(l, n):

	### Keybase proof

	I hereby claim:

	* I am mr-karan on github.
	* I am mrkaran (https://keybase.io/mrkaran) on keybase.
	* I have a public key whose fingerprint is CC91 6602 7F75 21FB 117A 90C4 06BD 5EE8 C167 6946

	To claim this, I am signing this object:

	import paramiko

	ip='server ip'
	port=22
	username='username'
	password='password'

	cmd='some useful command'

	ssh=paramiko.SSHClient()

	FROM alpine:latest
	COPY ./arg.sh /
	ENTRYPOINT ["/arg.sh"]