Making Docker and Kubernetes a success at your Company
0 likes154 views
The document discusses the challenges and advantages of adopting Docker and Kubernetes within companies, emphasizing the importance of avoiding customized setups to reduce costs. It highlights Kubernetes as a fundamental tool for maintaining scalability and efficiency, alongside the integration of metrics and monitoring tools to optimize resources. The text also touches on deployment strategies and improving operations, suggesting that starting with a clean slate can lead to better maintainability and reduced errors.
Making Docker and Kubernetes a success at your Company
- 2. and how to make it a success at your company!
- 4. Right choice for everyone
- 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
- 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
- 29. Initial problems: - not allowed - it is difficult - another team - hardware - metrics - maintainability - scaleability
- 32. money
- 34. ghost resources?
- 37. You are not saying: 10 machines
- 39. Kubernetes you don’t worry about resources
- 40. auto-scaling
- 48. what can they inject? - prometheus - grafana
- 49. service-mesh - envoy - istio - conduit
- 50. inject trust?
- 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
- 54. Ingress
- 57. Better monitoring Less coordination Save money
- 58. So much free time now?
- 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
- 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