How to Package & Deploy Microservices
0 likes540 views
The document presents a guide on how to build, package, and deploy microservices using Docker and related tools like Kaniko, Docker Compose, and Helm. It discusses best practices for creating Docker images, the benefits of using Kaniko to build images without privileges, and outlines the features of Helm 3.0 and Cloud Native Application Bundles (CNAB) for managing multi-container applications. The agenda includes practical demos and resources for further exploration of these technologies.
How to Package & Deploy Microservices
- 1. Make Your Data Work For You How to Package & Deploy Microservices Nico Meisenzahl February 2019
- 2. Speakers Daniel Klas @panagenda Inbound Marketing Coordinator panagenda Nico Meisenzahl @nmeisenzahl Consultant panagenda Join the conversation using #DevOps & @panagenda
- 3. Agenda 1. Build Docker Images with Kaniko 2. Compose & Helm 3. Future (Helm 3.0 & Cloud Native Application Bundle)
- 4. Everything starts with a Dockerfile • Describes the Image • Best practises – choose the base image wisely – use multi-stage builds – combine commands into few instructions as possible – use curl/wget for non-persistent files (installer, etc.) – reduce waste – know how caching works 4
- 5. Image build process • “docker build” is the common way • locally – available with every Docker installation → we love it and it just works • containerized – mostly used in build pipelines – Docker-in-Docker (DinD) is needed → Security issues! • Docker daemon needs to be mounted • privileged flag is needed • not allowed in a K8s environment (hopefully) → could be better... 5
- 6. Kaniko can help • Builds Images without privileges in a container • developed by Google • part of the Knative serverless stack – Istio, Kaniko, Knative • Docker Image: http://gcr.io/kaniko-project/executor • More details: https://github.com/GoogleContainerTools/kaniko 6
- 7. Kaniko (Demo) • can be used with – “docker run” – as a Pod definition (Kubernetes) – in build pipelines – ... 7
- 8. Running a microservice can’t be that hard... docker run -d my-microservice 8
- 9. But, what if ... • your application is based on various microservices? • you would like to have a portable and easy deployment? → you will need a tool to package your application 9
- 10. Where Compose and Helm can help (Demo) • can be used to define and run bundled multi-container Microservices – portable deployments & updates – versioning & rollbacks (Helm only) – Repositories (Helm, docker-app) • Compose can be used with – pure Docker – Swarm – docker-app • Helm is the defacto default package manager for Kubernetes • more details – https://helm.sh – https://docs.docker.com/compose – https://github.com/docker/app 10
- 11. Helm 3.0 • removal of Tiller – Client-only – based on RBAC, CRD • embedded Lua engine – optional and mixable – more flexible – work with objects not YAML • Chart repo authentication & upload – helm login – helm push • more details: https://www.youtube.com/watch?v=XUqNLhFWbl8 11
- 12. Helm 2 vs. 3 (Lua) 12
- 13. CNAB (Cloud Native Application Bundle) • a spec for packaging distributed apps • designed by Microsoft, Docker, bitnami & HashiCorp • is not platform-specific: Containers, Functions, VMs, IaaS and PaaS – Compose / Helm / Kubernetes – Ansible / Terraform – Azure , OpenStack on-premises, …. • a CNAB is defined by a bundle.json and will be deployed by a invocation image 13
- 14. CNAB (Cloud Native Application Bundle) • CLIs supporting CNAB specs – duffle by Microsoft – docker-app by Docker – ... • CNABs can be pushed to Docker Hub (using docker-app) • more details – https://cnab.io – https://github.com/deislabs/cnab-spec – https://duffle.sh – https://github.com/docker/app – https://medium.com/01001101/cloud-native-application-bundle-a-spec-for-packagi ng-distributed-apps-7f1a7e3fc6fe 14
- 15. Questions? • Slides – http://slideshare.net/nmeisenzahl • Demos – https://gitlab.com/nmeisenzahl/docker-meetup-package-deploy 15
- 16. Headquarters, Austria: panagenda GmbH (Ltd.) Schreyvogelgasse 3/10 AT 1010 Vienna Phone: +43 1 89 012 89 Fax: +43 1 89 012 89-15 E-Mail: info@panagenda.com Headquarters, Germany: panagenda GmbH (Ltd.) Lahnstraße 17 DE 64646 Heppenheim Phone: +49 6252 67 939-00 Fax: +49 6252 67 939-16 E-Mail: info@panagenda.com USA: panagenda Inc. 60 State Street, Suite 700 MA 02109 Boston Phone: +1 617 855 5961 Fax: +1 617 488 2292 E-Mail: info@panagenda.com Germany: panagenda Consulting GmbH (Ltd.) Donnersbergstrasse 1 DE 64646 Heppenheim Phone: +49 6252 67 939-86 Fax: +49 6252 67 939-16 E-Mail: info@panagenda.com The Netherlands: Trust Factory B.V. 11th Floor, Koningin Julianaplein 10 NL 2595 AA The Hague Phone: +31 70 80 801 96 E-Mail: info@trust-factory.com © 2007-2015 panagenda Make Your Data Work For You