joshrosso

" -----------------------------------------------------------------------------
" plugins
" -----------------------------------------------------------------------------
call plug#begin('~/.vim/plugged')

Plug 'mileszs/ack.vim'
Plug 'kien/ctrlp.vim' "file fuzzy search
Plug 'scrooloose/nerdtree'
Plug 'NLKNguyen/papercolor-theme'
Plug 'majutsushi/tagbar'

joshrosso

Lake City / Gunnison Climbing

Drive to Lake City

• distance: 5 hours : 266 miles
• map: Boulder to Lake City
• route: 289->US 50W

Climbing Options

joshrosso

PS1='\u (\e[38;5;198m\w\e[0m) [\e[38;5;148m$(git branch 2>/dev/null | grep '^*' | colrm 1 2)\e[0m]\n\$ '

joshrosso

This details an attempt to specify how docker should timeout on nameserver resolutions.

1. systemd-resolved is on

root@ip-172-31-22-219:~ip-172-31-22-219 ~ # systemctl status systemd-resolved --no-pager ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: disabled) Active: active (running) since Mon 2017-09-11 15:32:43 UTC; 7min ago Docs: man:systemd-resolved.service(8)

joshrosso

apiVersion: "alpha.projectcalico.org/v1"
kind: SystemNetworkPolicy
metadata:
  name: allow-ingress-in-namespace
  namespace: kube-system
spec:
  order: 0
  selector: calico/k8s_ns == 'policy-demo'
  ingress:
  - action: allow

joshrosso

These are my notes testing:

• Calico on Tectonic
• New (and undocumented) SystemNetworkPolicy TPR introduced in calico-lib

1. Clone the repo containing the Calico additions and switch to the appropriate branch.

$ git clone abhinavdahiya git@github.com:abhinavdahiya/tectonic-installer.git &&\
   cd tectonic-installer &&\
 git checkout calico_policy_support

joshrosso

policy steps

Create namespace

$ kubectl create ns policy-demo

joshrosso

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: default-http-backend
  labels:
    k8s-app: default-http-backend
  namespace: kube-system
spec:
  replicas: 1
  template:

joshrosso

# This ConfigMap can be used to configure a self-hosted Canal installation.
kind: ConfigMap
apiVersion: v1
metadata:
  name: canal-config
  namespace: kube-system
data:
  # Configure this with the location of your etcd cluster.
  etcd_endpoints: "http://$YOUR_ETCD_HOST:2379"

joshrosso

#!/bin/bash

sed -i 's/coreos\/hyperkube\:v1.5.2\_coreos\.1/joshrosso\/hyperkube\:special-cni/' manifests/kube-apiserver.yaml manifests/kube-proxy.yaml manifests/kube-scheduler.yaml manifests/kube-controller-manager.yaml
sed -i 's/coreos\/bootkube/joshrosso\/bootkube/' bootkube-start