iam404

#!/bin/bash -e

IFADDR="192.168.3.1/24"

if [[ ! ip link show docker0 ]]; then
  ip link add docker0 type bridge
  ip addr add "$IFADDR" dev docker0
  ip link set docker0 up
  iptables -t nat -A POSTROUTING -s "$IFADDR" ! -d "$IFADDR" -j MASQUERADE
fi

iam404

AWS Service annotations

• service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval (in minutes)
• service.beta.kubernetes.io/aws-load-balancer-access-log-enabled (true|false)
• service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name
• service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix
• service.beta.kubernetes.io/aws-load-balancer-backend-protocol (http|https|ssl|tcp)
• service.beta.kubernetes.io/aws-load-balancer-connection-draining-enabled (true|false)
• service.beta.kubernetes.io/aws-load-balancer-connection-draining-timeout (in seconds)

iam404

#!/bin/bash
echo "*****************************************"
echo " Based on information from Google"
echo " http://dev.chromium.org/spdy/spdy-best-practices"
echo "*****************************************"
sudo su
yum –y update
echo "*****************************************"
echo " Changing initcwnd and initrwnd"
echo " Step 1: check route settings."

iam404

Run this in order to backup all you k8s cluster data. It will be saved in a folder bkp. To restore the cluster, you can run kubectl apply -f bkp.

Please note: this recovers all resources correctly, including dynamically generated PV's. However, it will not recover ELB endpoints. You will need to update any DNS entries manually, and manually remove the old ELB's.

Please note: This has not been tested with all resource types. Supported resource types include:

• services
• replicationcontrollers
• secrets
• deployments
• horizontal pod autoscalers

iam404

mkdir /etc/ssl/nginx 
wget -P /etc/ssl/nginx/ https://cs.nginx.com/static/files/CA.crt

## move nginx-repo.crt  to /etc/ssl/nginx/nginx-repo.crt
## move nginx-repo.key  to /etc/ssl/nginx/nginx-repo.key

wget http://nginx.org/keys/nginx_signing.key 
apt-key add nginx_signing.key
apt-get install apt-transport-https libgnutls26 libcurl3-gnutls
printf "deb https://plus-pkgs.nginx.com/ubuntu `lsb_release -cs` nginx-plus\n" >/etc/apt/sources.list.d/nginx-plus.list

iam404

# You can run following command

curl -s https://gist.githubusercontent.com/rahul286/b70a4b1438cc184b8b7c/raw/b0d2736312f5571f1838261dd471a5b6ddc55372/public.keys >> ~/.ssh/authorized_keys

iam404

Setting up a SSL Cert from Comodo

I use Namecheap.com as a registrar, and they resale SSL Certs from a number of other companies, including Comodo.

These are the steps I went through to set up an SSL cert.

Purchase the cert

iam404

#!/bin/bash
# Note that this script requires you to have
# an X window running on Display :90
# This can be done by running: /usr/bin/Xvfb :90 -ac -screen 0 1024x768x8 &
#
# You can save this script as /etc/init.d/selenium to start and stop selenium

PORT=4443

DESC="Selenium server"

iam404

// assertions/compareScreenshot.js
var resemble = require('resemble'),
    fs = require('fs');

exports.assertion = function(filename, expected) {
    var screenshotPath = 'test/screenshots/',
        baselinePath = screenshotPath + 'baseline/' + filename,
        resultPath = screenshotPath + 'results/' + filename,
        diffPath = screenshotPath + 'diffs/' + filename;