Talk presented at Cloud Native London meetup, 4th July 2017 Demos available online @ https://www.katacoda.com

1. The Challenges of Becoming Cloud-Native
Ben Hall
Ben@Katacoda.com
Katacoda.com

3. Hands up if one applies to your team
• We need to deploy Windows applications
• We’re still managing/refactoring our monolith
• We may need to deploy 100s of microservices
• We have “big data”
• We’re not sure what Kubernetes/CloudNative is…
• We need to teach Kubernetes/CloudNative ...

6. The challenges of becoming
cloud-native
• Deploying Windows Containers onto
Kubernetes
• Kubernetes Extending Traditional Applications
• Handling Microservices with Istio

7. @Ben_Hall / Blog.BenHall.me.uk
WHOAMI?

8. Katacoda Interactive Technical Training Platform
Katacoda.com

10. Windows Containers

11. Cloud-Native Impact

13. > type Dockerfile
FROM microsoft/iis:windowsservercore-10.0.14393.693
SHELL ["powershell", "-command"]
RUN Install-WindowsFeature NET-Framework-45-ASPNET; Install-
WindowsFeature Web-Asp-Net45
RUN Remove-Website -Name 'Default Web Site';
mkdir c:NerdDinner;
New-Website -Name 'nerd-dinner'
-Port 80 -PhysicalPath 'c:NerdDinner'
-ApplicationPool '.NET v4.5‘
EXPOSE 80
COPY NerdDinner c:NerdDinner

14. PS C:> docker run -d -p 80:80
nerddinner

15. Cloud Native + Windows?

16. Microsoft & Red Hat
https://github.com/kubernetes/features/issues/116

20. Does your application need to be
Kubernetes aware?

21. Ingress Routing / Session Affinity /
Local Only

22. apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: test-ingress
spec:
rules:
- host: katacoda.com
http:
paths:
- path: /payments
backend:
serviceName: orders
servicePort: 80
- backend:
serviceName: app
servicePort: 80

23. apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: test-ingress
spec:
rules:
- host: katacoda.com
http:
paths:
- path: /payments
backend:
serviceName: orders
servicePort: 80
- backend:
serviceName: app
servicePort: 80

24. apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: nginx-test
annotations:
kubernetes.io/ingress.class: "nginx"
ingress.kubernetes.io/affinity: "cookie"
ingress.kubernetes.io/session-cookie-name: "route"
ingress.kubernetes.io/session-cookie-hash: "sha1"
spec:
rules:
- host: stickyingress.example.com
http:
paths:
- backend:
serviceName: nginx-service
servicePort: 80
path: /

25. apiVersion: v1
kind: Service
metadata:
name: echoheaders-nodeport
annotations:
service.beta.kubernetes.io/external-traffic: OnlyLocal
labels:
app: echoheaders-nodeport
spec:
type: NodePort
ports:
- port: 80
nodePort: 30416
targetPort: 8080
protocol: TCP
name: http
selector:
app: echoheaders

26. Pods, Sidecars, Controllers

27. Creating a Custom Controller
Controller Manager Scheduler
API Server
etcd

28. Creating a Custom Controller
Controller Manager Scheduler
API Server
etcd
Custom Controller
Custom Controller
Custom Controller

29. Kelsey’s Secrets Controller

30. apiVersion: extensions/v1beta1
kind: ReplicaSet
metadata:
name: secrets-controller
labels:
app: secrets-controller
spec:
replicas: 1
template:
metadata:
labels:
name: secrets-controller
spec:
containers:
- name: secrets-controller
image: gcr.io/hightowerlabs/secrets-controller:0.0.3
env:
- name: NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
args:
- "-namespace=$(NAMESPACE)"
- "-secretName=oscon"
- "-vault-addr=http://vault-0.vault.$(NAMESPACE).svc.cluster.local:8200"
- "-vault-token=3e4a5ba1-oscon-422b-d1db-844979cab098”

31. func main() {
k8sClient, err = k8s.NewInClusterClient()
k8sClient.Namespace = namespace
// Create a Vault client.
vaultClient, err = vaultapi.NewClient(vaultapi.DefaultConfig())
vaultClient.SetToken(vaultToken)
go func() {
for {
time.Sleep(10 * time.Second)
err := syncSecret()
if err != nil {
log.Println(err)
}
}
}()
quit := make(chan os.Signal, 1)
signal.Notify(quit, syscall.SIGINT, syscall.SIGTERM)
<-quit
log.Printf("Shutdown signal received, exiting...")
}

32. Pods and Sidecars

34. Sidecars as adapters

35. Kubernetes DNS

36. Kubernetes DNS

37. Statd to Prometheus sidecar

38. Your Application
statsd_exporter
localhost:9125
Prometheus
Pod 1 Pod 2

39. DaemonSet + Prometheus

40. apiVersion: v1
kind: Service
metadata:
annotations:
prometheus.io/scrape: 'true'
labels:
app: node-exporter
name: node-exporter
name: node-exporter
spec:
clusterIP: None
ports:
- name: scrape
port: 9100
protocol: TCP
selector:
app: node-exporter
type: ClusterIP

42. https://www.linkedin.com/pulse/dependency-hell-microservices-how-avoid-nabil-hijazi

44. Service Mesh

45. Service Mesh
• A service mesh is a dedicated infrastructure
layer for making service-to-service
communication safe, fast, and reliable.
• If you’re building a cloud native application,
you need a service mesh!
https://blog.buoyant.io/2017/04/25/whats-a-service-mesh-and-why-do-i-need-one/

50. Prometheus Insights

51. Zipkin Integration

52. Service-to-Service TLS Encryption

53. Kuber… What?

54. Teach your teams cloud-native

58. Thank you
@Ben_Hall
Ben@Katacoda.com
Katacoda.com