jmcdice

# Install gcloud

  export CLOUD_SDK_REPO="cloud-sdk-$(lsb_release -c -s)"
  echo "deb http://packages.cloud.google.com/apt $CLOUD_SDK_REPO main" | sudo tee -a /etc/apt/sources.list.d/google-cloud-sdk.list
  curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
  apt-get -y update
  apt-get -y --allow-unauthenticated install google-cloud-sdk kubectl

# Install GCSFuse

jmcdice

## Install Utils:
  $ sudo apt-get update
  $ sudo apt-get install tmux youtube-dl htop ccze vlc

## Install and use youtube-dl
  $ youtube-dl https://www.youtube.com/watch?v=cC9r0jHF-Fw
  $ youtube-dl -F <video> (list video formats)
  $ youtube-dl -f <index> <video> download video at <format> --output fish.webm

## Example

jmcdice

# Deploy Concourse to PKS

  $ helm init --wait
  $ kubectl create serviceaccount --namespace kube-system tiller
  $ kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
  $ kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'
  $ helm install --name concourse stable/concourse

# View Concourse via your browser
  $ export POD_NAME=$(kubectl get pods --namespace default|perl -lane 'print @F[0] if /web/')

jmcdice

FROM ubuntu:latest

ENV DEBIAN_FRONTEND noninteractive
RUN sed -i 's#http://archive.ubuntu.com/#http://ubuntu.mirrors.tds.net/ubuntu/#' /etc/apt/sources.list

# built-in packages
RUN apt-get update
RUN apt-get -o Dpkg::Options::='--force-confold' --force-yes -fuy dist-upgrade

# common utils apt

jmcdice

Step-by-Step Network Policy Deployment Plan

Summary: How These Network Policies Work

Network policies in Kubernetes are like traffic rules for your application's components. They control which parts of your application can talk to each other and how. Here's a simple breakdown of how the policies in this guide work:

1. Zero-Trust Starting Point: We begin by assuming no communication is allowed. It's like having walls between all parts of your application.
2. Allowing Necessary Communication: We then create "doors" in these walls, but only where needed. For example:
   • We allow components in the same environment (like production) to talk to each other.

• We let the backend talk to the frontend, but not the other way around.