Pedro Sanders psanders

To expose UDP service via NGINX, you need four things:

Add port definition to DaemonSet (by default it only exposes TCP/80 and TCP/443)
Run your app
Create a service exposing your app
Add service definition to ConfigMap udp-services in the ingress-nginx namespace.

See https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/exposing-tcp-udp-services.md

Add port definition to DaemonSet

>>> docker exec -it CONTAINERID /bin/sh
/app # telnet
/bin/sh: telnet: not found

/app # apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
v3.7.0-243-gf26e75a186 [http://dl-cdn.alpinelinux.org/alpine/v3.7/main]
v3.7.0-229-g087f28e29d [http://dl-cdn.alpinelinux.org/alpine/v3.7/community]

Getting Started

Make sure Docker is installed!

Get your Minio endpoint url, accesskey, and secretkey ready!

Install Docker Plugin

docker plugin install rexray/s3fs \

Docker Swarm with Macvlan, Consul and Autoscaling

TL;DR:

This will get you routable containers with IPs on your existing subnets, advertising to Consul. They will also be scalable and placed across a cluster of Swarm hosts. It's assumed that you are already running Consul, so if not, there are a ton of tutorials out there. It's also assumed you know how to install Docker and various Linux kernels.

Bonus: We add an autoscaling API called Orbiter (https://gianarb.it/blog/orbiter-the-swarm-autoscaler-moves).

I just want to run containers, like now, on my existing infrastructure and networks!

So you have an existing environment. You use Consul for service discovery. Life is good. Containers are now a thing and you want to work them in without having to worry about overlay networking or reverse proxies. You also don't want to add extra latency (as some naysayers could use it as fuel to kill your hopes and dreams). Lastly, you don't have a lot of time to invest in a complex orchestration tool, such a

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

Macvlan, Ipvlan and 802.1q Trunk Driver Notes

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

URL

<The URL Structure (path only, no root url)>
Method:

	Making routr working on k8s and remote cli managment
	===
	### Prepare
	- Pls make sure you have traefik in your k8s, if you don't, please [install it](https://github.com/traefik/traefik-helm-chart)
	- [Install routr using helm](https://artifacthub.io/packages/helm/routr/routr)
	- [install rctl](https://routr.io/docs/administration/cli/installation/) in you pc, or management laptop, etc.
	### Create ingressroute for routr
	- update you traefik, create two entrypoints for tcp/udp
	```yaml=
	@ traefik/values.yaml:206 @ ports:

	# source : http://code.google.com/p/natvpn/source/browse/trunk/stun_server_list
	# A list of available STUN server.

	stun.l.google.com:19302
	stun1.l.google.com:19302
	stun2.l.google.com:19302
	stun3.l.google.com:19302
	stun4.l.google.com:19302
	stun01.sipphone.com
	stun.ekiga.net

	[
	{"group":"US (Common)",
	"zones":[
	{"value":"America/Puerto_Rico","name":"Puerto Rico (Atlantic)"},
	{"value":"America/New_York","name":"New York (Eastern)"},
	{"value":"America/Chicago","name":"Chicago (Central)"},
	{"value":"America/Denver","name":"Denver (Mountain)"},
	{"value":"America/Phoenix","name":"Phoenix (MST)"},
	{"value":"America/Los_Angeles","name":"Los Angeles (Pacific)"},
	{"value":"America/Anchorage","name":"Anchorage (Alaska)"},