duyhenryer

iptables cheat sheet

• https://accelazh.github.io/network/Play-With-iptables

Concepts

iptables defines tables, which group features:

• filter: use it to filter traffic
• nat: use it to implement NAT
• raw: use it to define which connections iptables should track (stateful firewall)
• mangle: use it to change some fields in packets (e.g., TTL)
• security: use it to define access control

duyhenryer

JWT Kong Example

• Get and Start Kong and Co

git clone git@github.com:Mashape/docker-kong.git
cd docker-kong/compose
docker-compose up

• Create Kong API Route

duyhenryer

# This file is:  ~/.ssh/config

# You may have other (non-CodeCommit) SSH credentials stored in this
# config file – in addition to the CodeCommit settings shown below.

# NOTE: Make sure to run [ chmod 600 ~/.ssh/config ] after creating this file!

# Credentials for Account1
Host awscc-account1                                 # 'awscc-account1' is a name you pick
  Hostname git-codecommit.us-east-1.amazonaws.com   # This points to CodeCommit in the 'US East' region

duyhenryer

How to register Rancher managed Kubernetes clusters in Argo CD

Registering Rancher managed clusters in Argo CD doesn't work out of the box unless the Authorized Cluster Endpoint is used. Many users will prefer an integration of Argo CD via the central Rancher authentication proxy (which shares the network endpoint of the Rancher API/GUI). So let's find out why registering clusters via Rancher auth proxy fails and how to make it work.

Hint: If you are just looking for the solution scroll to the bottom of this page.

Why do i get an error when running argocd cluster add?

Service Account tokens and the Rancher authentication proxy

duyhenryer

Retrieve hosted zones with aws route53 list-hosted-zones then enter the zone Id below:

aws route53 list-resource-record-sets --hosted-zone-id "/hostedzone/xxxxxxxxxxx" | \
   jq -r '.ResourceRecordSets[] | [.Name, .Type, (.ResourceRecords[]? | .Value), .AliasTarget.DNSName?]  | @tsv'

duyhenryer

# ~/.config/starship.toml

[battery]
full_symbol = "🔋"
charging_symbol = "🔌"
discharging_symbol = "⚡"

[[battery.display]]
threshold = 30
style = "bold red"

duyhenryer

# Start minikube
minikube ip || minikube start --vm-driver=kvm2 --cpus=8 --memory=10000 --insecure-registry=192.168.0.0/16
for addon in default-storageclass ingress storage-provisioner
do
  minikube addons list | grep $addon | grep -q enabled || minikube addons enable $addon
done
# Init helm
helm repo add gitlab https://charts.gitlab.io/
helm repo update
# Gensecrets

duyhenryer

This will guide you through setting up a replica set in a docker environment using.

• Docker Compose
• MongoDB Replica Sets
• Mongoose
• Mongoose Transactions

Thanks to https://gist.github.com/asoorm for helping with their docker-compose file!

duyhenryer

#MongoDB 3.2.x Replica Sets on AWS EC2 A MongoDB replica set provides a mechanism to allow for a reliable database services. The basic replica set consists of three servers, a primary, a secondary and an arbitrator. The primary and secondary both hold a copy of the data. The arbitrator is normally a low spec server which just monitors the other servers and help with the failover process. In production, there can be more than three servers.

To setup mongo as a replica set on Amazon Web Services EC2 you need to first setup a security group with ssh on port 22 and mongodb on port 27017. You then need to create three servers. Select Ubuntu 14.04 LTS x64 and a micro (or bigger depending on your database size, ideally you should have enough memory to match your database size) instance for the primary and secondary and a nano instance for the arbitrator.

##Adjust the File System on each Server The operating system by default will update the last access time on a file. In a high data throughput database application

duyhenryer

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.