Steve Coffman StevenACoffman

Functions As A Service

kubeless, fission, funktion, openwhisk, faas seem to the most common in FAAS solutions. Nuclio is also interesting.

Github Star Trend:

This is just a picture of this link from August 2, 2017

You had ONE JOB -- A Kubernetes job.

Let's take a look at how Kubernetes jobs are crafted. I had been jamming some kind of work-around shell scripts in the entrypoint* for some containers in the vnf-asterisk project that Leif and I have been working on. And that's not perfect when we can use Kubernetes jobs, or in their new parlance, "run to completion finite workloads" (I'll stick to calling them "jobs"). They're one-shot containers that do one thing, and then end (sort of like a "oneshot" of systemd units, at least how we'll use them today). I like the idea of using them to complete some service discovery for me when other pods are coming up. Today we'll fire up a pod, and spin up a job to discover that pod (by querying the API for info about it), and put info into etcd. Let's get the job done.

This post also exists as a [gist on github](https

Registration

curl -v -X POST -H "Accept: application/xml" -H "Content-type: application/xml" --data @reg.xml http://localhost:8761/eureka/apps/test

Listing

curl -X GET -H "Accept: application/json" http://localhost:8761/eureka/apps

This helpful advice was from @tsupertramp

for a in `kubectl get pods  -n kube-system |grep kube-dns |grep -v autoscaler |cut -d ' ' -f 1 `;do for b in kubedns dnsmasq sidecar;do kubectl logs -n kube-system $a -c $b  > $a-$b.log;done;done

=> Then you have logfiles of dns in your current directory. Then just look through the log files if there is anything like “warning” or “error”

It searches your pod names and then shows logs of each pods containers (it has three kubedns / dnsmasq / sidecar)

Then check output of:

● Manual
- ○ Kubernetes the Hard Way (kubernetes-the-hard-way)
● Config management (Cloud Formation) Automating Manual method
- ○ kube-aws
- ○ kubernetes-on-aws
● Containerized
- ○ Rancher, Deis, etc.
● Self-Hosted Kubernetes
- ○ kubeadm, tectonic, bootkube

MicroService Proxy Gateway Solutions

Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.

Github Star Trend:

This is just a picture of this link from March 2, 2019

Originally, I had included some other solution

	#!/usr/bin/env python
	import boto.vpc
	import time

	REGION_NAME = 'us-west-2'
	AMI_ID = 'ami-8e27adbe' # Amazon Linux AMI

	conn = boto.vpc.connect_to_region(REGION_NAME)

	# Create a VPC

	curl -k -X GET \
	-H "Authorization: Bearer $(cat /var/run/secrets/kubernetes.io/serviceaccount/token)" \
	https://$KUBERNETES_PORT_443_TCP_ADDR:$KUBERNETES_SERVICE_PORT_HTTPS

	defaults write com.apple.LaunchServices/com.apple.launchservices.secure LSHandlers -array-add \
	'{LSHandlerContentType=public.plain-text;LSHandlerRoleAll=com.macromates.textmate.preview;}'