Go to any directory and clone repo with sources.
cd ~
git clone https://github.com/certbot/certbot| #!/usr/bin/env bash | |
| # Documentation | |
| # https://docs.gitlab.com/ce/api/projects.html#list-projects | |
| NAMESPACE="YOUR_NAMESPACE" | |
| BASE_PATH="https://gitlab.example.com/" | |
| PROJECT_SEARCH_PARAM="" | |
| PROJECT_SELECTION="select(.namespace.name == \"$NAMESPACE\")" | |
| PROJECT_PROJECTION="{ "path": .path, "git": .ssh_url_to_repo }" |
Unless specified otherwise in Vagrantfile, the IP address of the host (the computer running Vagrant) from the perspective of the guest
(the VM being run by Vagrant) is: 10.0.2.2
If that IP address doesn't work, then examination of Vagrantfile should reveal directives that changed it from its default value.
If an IP address can't be found in Vagrantfile, then the following command will probably reveal it:
route -A inetdocker pull gcr.io/google_containers/kube-apiserver-amd64:v1.5.0
docker pull gcr.io/google_containers/kube-controller-manager-amd64:v1.5.0
docker pull gcr.io/google_containers/kube-proxy-amd64:v1.5.0
docker pull gcr.io/google_containers/kube-scheduler-amd64:v1.5.0
docker pull weaveworks/weave-npc:1.8.2
docker pull weaveworks/weave-kube:1.8.2
Wednesday 26/07/2017
tl;dr - Kubernetes is a container orchestration engine.
tl;dr - Microservices are software components that are independently deployable and scalable.
Kubeadm Documentation : https://kubernetes.io/docs/getting-started-guides/kubeadm/
Wednesday 26/07/2017
tl;dr - An Ingress is a collection of rules that allow inbound connections to reach the cluster services.
tl;dr - The ingress-controller is just a reverse proxy that forwards incoming requests based on the URL and host header (if used).
| vault mount pki | |
| vault mount -path=pki1 pki | |
| vault mount -path=pki2 pki | |
| vault mount -path=pki3 pki | |
| vault mount-tune -max-lease-ttl=87600h pki | |
| vault mount-tune -max-lease-ttl=87600h pki1 | |
| vault mount-tune -max-lease-ttl=87600h pki2 | |
| vault mount-tune -max-lease-ttl=87600h pki3 | |
| vault write pki/root/generate/internal common_name="Vault Testing Root Authority" ttl=87600h |
| #!/bin/bash -e | |
| # Setup a Root CA in vault | |
| # Generate and sign an Intermediate cert | |
| # | |
| # Requires: | |
| # * A running vault server already initialzed and unsealed | |
| # * Environment variable VAULT_TOKEN is set | |
| # * vault cli (https://www.vaultproject.io) | |
| # * httpie (https://github.com/jkbrzt/httpie) |