Don't miss this talk if you are critical about how Kubernetes can be helpful to you. We will talk about the benefits and downsides of using Kubernetes and how to take docker and kubernetes from theory to practice as your company. Story of how we took Connected Cars from nothing to a full self-serving platform in one year. Key takeaways: How to tame the microservice hell The best adoption starts from the developers Repeatable builds Docker and Continues Integration is the 20% effort with 80% gains Kubernetes is complex but worth it, takes the scary out of deploying

1. Docker
&
Kubernetes

2. and how to
make it a success
at your company!

3. Kubernetes
is
Hard

4. Right choice
for everyone

5. There is
the reason

6. Do not
reinvent the
wheel

7. x companies
=
x different setups

8. = lot of money
to consultants

9. Nobody wants
to work on old
projects

10. unless..

11. they are
paid a lot $$$

12. let us analyze!

13. why is it so
nice to start
from scratch?

14. new
framework?

15. you can actually find
the documentation

16. it starts quickly

17. inherit
knowledge

19. Why don’t
we start
from scratch?

20. - you are not allowed
- it is difficult
- other teams
- hardware
- metrics
- maintainability
- scalability

21. My stories

22. IT consultants
The bus-factor?

23. Danish Energy
Provider
Platform?

24. Ad agency
Resource control?

25. Job Portal
Maintainability?

26. Kubernetes
=
commodity

28. Kubernetes
=
ground layer

29. Initial problems:
- not allowed
- it is difficult
- another team
- hardware
- metrics
- maintainability
- scaleability

30. They can be
solved,
once!

31. framework
also
building blocks

32. money

33. saving money
by
raising utilization

34. ghost
resources?

35. Kubernetes give
insights &
commitments

36. Deployment:
10 replicas

37. You are not
saying:
10 machines

38. Over-provisioning?!
RAM
CPU
DISK

39. Kubernetes you
don’t worry
about resources

40. auto-scaling

41. how does
autoscaling
nodes work?

42. current
load
total
capacity<

43. What else
than saving
money?

44. Metrics
are hard?

45. Metrics
=
insights for scaling

46. ops devops/devs
appdeploy

47. ops devops/devs
app
deploy
inject

48. what can they
inject?
- prometheus
- grafana

49. service-mesh
- envoy
- istio
- conduit

50. inject trust?

51. How does it
work?
RBAC

52. kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: gitkube
subjects:
- kind: ServiceAccount
name: gitkube
namespace: kube-system
roleRef:
kind: ClusterRole
name: cluster-admin
apiGroup: rbac.authorization.k8s.io

53. micro-services
0
20
40
60
80
maintain create

54. Ingress

55. Ingress
Easy micro-services

56. Ingress
complex micro-services
500
200

57. Better monitoring
Less coordination
Save money

58. So much free
time now?

59. Chaos
Engineering?

60. Getting more
responsibility
with
more tools

61. Azure Container
Instances
&
AWS FarGate

62. Virtual Kube-let
=
Per sec billing

63. Reach a new level
and moved
beyond bare metal

64. but my boss
wouldn’t
let me!

65. Kubernetes is
small -
start on your own!

66. You are making less
errors, focusing
more on security
and insights

67. Connected Cars
on
Kubernetes

68. Kubernetes
New Types

69. apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
name: remotes.gitkube.sh
spec:
group: gitkube.sh
version: v1alpha1
scope: Namespaced
names:
plural: remotes
singular: remote
kind: Remote
shortNames:
- rem

70. apiVersion: gitkube.sh/v1alpha1
kind: Remote
metadata:
name: sampleremote
namespace: default
spec:
# Insert ssh-keys for allowing users to git push
authorizedKeys:
- "ssh-rsa your-ssh-public-key"
# Provide registry details: https://github.com/hasura/gitkube/blob/master/docs/registry.md
registry:
url: "docker.io/user"
credentials:
secretRef: regsecret # Name of docker-registry secret
# Define deployment rules
deployments:
- name: www # Name of K8s deployment which is updated on git push
containers:
- name: www # Name of container in the deployment which is built during git push
path: example/www # Docker build context path in the git repo
dockerfile: example/www/Dockerfile # Location of Dockerfile for the source code

71. Thank you!
kevin.simper@gmail.com
@kevinsimper