James Veitch darth-veitcher

Set up microk8s with Cilium for development

Microk8s is a Canonical project to provide a kubernetes environment for local development, similar to minikube but without requiring a separate VM to manage. These instructions describe setting it up for common development use cases with Cilium and may be helpful in particular for testing BPF kernel extensions with Cilium.

Microk8s will run its own version of docker for the kubernetes runtime, so if you have an existing docker installation then this may be confusing, for instance when building images the image may be stored with one of these installations and not the other. This guide assumes you will run both docker daemon instances, and use your existing docker-ce for building Cilium while using the microk8s.docker daemon instance for the runtime of your kubernetes pods.

Requirements

Linux with kernel 4.9 or newer ([Full Cilium Requirements](https://cilium.readthedocs.io/en/latest/install/system_requirements/?highlight=requiremen

These files contain the base configuration for ProPublica’s Tor hidden service mirror.

Of note:

We're using the nginx "subs_filter" and "headers more" modules to allow us to rewrite content and update headers, so that we can convert clearnet links into onion links, where possible.
Based on feedback we've received, we're using Unix sockets (instead of a 127.0.0.1:___ TCP port) where nginx listens internally for the inbound connection from Tor. This ensures that a firewall misconfiguration can't expose the site running in nginx, which is likely overkill for an already-public (clearnet) website; this may also slightly improve performance and reduce socket overhead, however.

If you try doing this and have issues using sudo service nginx restart due to leftover connections using the socket, you may have to nuke the previous sockets before starting a new nginx process:

If you haven’t worked with JavaScript in the last few years, these three points should give you enough knowledge to feel comfortable reading the React documentation:

We define variables with let and const statements. For the purposes of the React documentation, you can consider them equivalent to var.
We use the class keyword to define JavaScript classes. There are two things worth remembering about them. Firstly, unlike with objects, you don't need to put commas between class method definitions. Secondly, unlike many other languages with classes, in JavaScript the value of this in a method [depends on how it is called](https://developer.mozilla.org/en-US/docs/Web/Jav

Kubernetes on DigitalOcean with CoreOS

Let's look at an example of how to launch a Kubernetes cluster from scratch on DigitalOcean, including kubeadm, an Nginx Ingress controller, and Letsencrypt certificates.

Overview

Environment

We'll be creating a four-node cluster (k8s-master, k8s-000...k8s-002), load balancer, and ssl certificates.

TLS secured TCP exposed Docker daemon on Dokku host - setup

Create certificates
Edit Docker options
Restart Docker
Copy client certificates from host
(optional) Add remote endpoint in Portainer

Tested on a standard $5/mo DigitalOcean VPS running Ubuntu 16.04.

%title: Kubeception %author: @dghubble

// Youtube: https://www.youtube.com/watch?v=tlUiQa2JYQU

-> Kubeception

-> Experiments with QEMU/KVM on Kubernetes <-

	import json
	import logging
	import platform
	import sys
	import time
	import traceback

	class JSONFormatter:
	"""A formatter for the standard logging module that converts a LogRecord into JSON

	public class SettingsHelper
	{
	public void OpenAppSettings()
	{
	var intent = new Intent(Android.Provider.Settings.ActionApplicationDetailsSettings);
	intent.AddFlags(ActivityFlags.NewTask);
	var uri = Android.Net.Uri.FromParts("package", package_name, null);
	intent.SetData(uri);
	Application.Context.StartActivity(intent);
	}

	# Generate a new pgp key: (better to use gpg2 instead of gpg in all below commands)
	gpg --gen-key
	# maybe you need some random work in your OS to generate a key. so run this command: `find ./* /home/username -type d \| xargs grep some_random_string > /dev/null`

	# check current keys:
	gpg --list-secret-keys --keyid-format LONG

	# See your gpg public key:
	gpg --armor --export YOUR_KEY_ID
	# YOUR_KEY_ID is the hash in front of `sec` in previous command. (for example sec 4096R/234FAA343232333 => key id is: 234FAA343232333)

	# A virtualenv running Python3.6 on Amazon Linux/EC2 (approximately) simulates the Python 3.6 Docker container used by Lambda
	# and can be used for developing/testing Python 3.6 Lambda functions
	# This script installs Python 3.6 on an EC2 instance running Amazon Linux and creates a virtualenv running this version of Python
	# This is required because Amazon Linux does not come with Python 3.6 pre-installed
	# and several packages available in Amazon Linux are not available in the Lambda Python 3.6 runtime

	# The script has been tested successfully on a t2.micro EC2 instance (Root device type: ebs; Virtualization type: hvm)
	# running Amazon Linux AMI 2017.03.0 (HVM), SSD Volume Type - ami-c58c1dd3
	# and was developed with the help of AWS Support