Where the Helm are your binaries? as presented at Canada Kubernetes Meetups
•
1 like•383 views
Do you always know what’s going on with your product artifacts since the moment they are built by the CI server from Git sources all the way to being deployed by Helm into Kuberenetes? In this talk, we will show how to build a reliable and transparent pipeline from code to cluster using Git, Artifactory, Docker, Kubernetes, and Helm. We’ll show how you such a pipeline can help you answer the big questions: What to deploy, What is deployed, and what is this artifact that I am looking for. This kind of transparency is critical for today’s environments, and Kubernetes with Helm shouldn’t be an exception.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Where the Helm are your binaries? as presented at Canada Kubernetes Meetups
Similar to Where the Helm are your binaries? as presented at Canada Kubernetes Meetups (20)
More from Baruch Sadogursky
More from Baruch Sadogursky (20)
Recently uploaded
Recently uploaded (20)
Where the Helm are your binaries? as presented at Canada Kubernetes Meetups
- 1. Where the Helm are your binaries?
- 4. shownotes •www.jfrog.com/shownotes •Slides •Video (tomorrow!) •All the links! •Ratings, comments •Raffle! @jbaruch www.jfrog.com/shownotes
- 5. What the helm is helm? Dependency manager for Kubernetes @jbaruch www.jfrog.com/shownotes
- 6. What Dependency managers and printers have in common? @jbaruch www.jfrog.com/shownotes
- 11. How to deploy anything to k8s • Copy YAML • Paste YAML • Fix indents • Repeat @jbaruch www.jfrog.com/shownotes
- 12. Kubernetes resource { "kind": "Deployment", "apiVersion": "extensions/v1beta1", "metadata": { "name": "my-release-docker-app-chart" }, "spec": { "containers": [ { "name": "docker-app-chart", "image": "docker.artifactory/docker-app:1.0", @jbaruch www.jfrog.com/shownotes
- 13. Let’s build a new one! > docker build –t docker.artifactory/docker-app:1.1 @jbaruch www.jfrog.com/shownotes
- 14. One last thing… > sed –i.bak `s#docker.artifactory/docker-app:1.1#${imageTag}#` deployment.yaml @jbaruch www.jfrog.com/shownotes
- 16. Or just use :latest "image": "docker.artifactory/docker-app:latest" @jbaruch www.jfrog.com/shownotes
- 18. Encapsulated packages of Kubernetes deployments All this… xrayxray-analysis xray-event xray-indexer xray-nfs-server xray-persist Becomes this xray @jbaruch www.jfrog.com/shownotes
- 19. Powerful templating for descriptor files { "kind": "Deployment", "apiVersion": "extensions/v1beta1", "metadata": { "name": "{{ template "docker-app.fullname" . }}" }, "spec": { "containers": [ { "name": "{{ template "docker-app.name" . }}", "image": "{{ .Values.image.repository }}: {{ .Values.image.tag }}" @jbaruch www.jfrog.com/shownotes
- 20. Values: # Default values for docker-app. # This is a YAML-formatted file. # Declare name/value pairs to be passed into your templates. image: repository: docker.artifactory/docker-app tag: 1.1 secretName: regsecret pullPolicy: Always @jbaruch www.jfrog.com/shownotes
- 21. Simple! • Templates • Values • Metadata @jbaruch www.jfrog.com/shownotes
- 22. Chart <-> image relationship • Using templates we can reuse charts for multiple image versions • Chart versions != Image versions @jbaruch www.jfrog.com/shownotes
- 23. Kubernetes cluster control @jbaruch www.jfrog.com/shownotes
- 24. Two parts Helm client • Local chart development • Managing repositories • Interacting with the Tiller server Tiller Server • Listening for incoming requests from the Helm client • Combining a chart and configuration to build a release • Installing charts into Kubernetes, and then tracking the subsequent release • Upgrading and uninstalling charts by interacting with Kubernetes @jbaruch www.jfrog.com/shownotes
- 25. Helm commands >helm init >helm search >helm install >helm status >helm repo @jbaruch www.jfrog.com/shownotes
- 26. Helm repositories • Official repository - kubeapps.com @jbaruch www.jfrog.com/shownotes
- 28. Helm repositories • Official repository - kubeapps.com • Get a local one! • Option 1: Create your own: • Run an http server with index.yaml • Run helm repo index to generate one the index • Option 2: Use JFrog Artifactory • Universal Artifact Repository which supports Docker, Helm and everything else @jbaruch www.jfrog.com/shownotes
- 29. Use Artifactory: Take your metadata seriously Where the helm is my binary? @jbaruch www.jfrog.com/shownotes
- 30. The Age of Binaries IoT Docker Microservices DevOps CD CI Agile2001 2018
- 31. The big picture @jbaruch www.jfrog.com/shownotes
- 32. The big picture @jbaruch www.jfrog.com/shownotes
- 42. The big picture @jbaruch www.jfrog.com/shownotes
- 43. The big picture @jbaruch www.jfrog.com/shownotes
- 44. The big picture @jbaruch www.jfrog.com/shownotes
- 45. The big picture @jbaruch www.jfrog.com/shownotes
- 46. The big picture @jbaruch www.jfrog.com/shownotes
- 47. The big picture @jbaruch www.jfrog.com/shownotes
- 48. The big picture @jbaruch www.jfrog.com/shownotes
- 49. The big picture @jbaruch www.jfrog.com/shownotes
- 50. The big picture @jbaruch www.jfrog.com/shownotes
- 51. The big picture @jbaruch www.jfrog.com/shownotes
- 52. Who cares about those binaries anyway? @jbaruch www.jfrog.com/shownotes
- 53. Demo time Talk is cheap, show me the code! @jbaruch www.jfrog.com/shownotes
- 55. QA and links •www.jfrog.com/shownotes •Slides •Video (tomorrow!) •All the links! •Ratings, comments •Raffle! @jbaruch www.jfrog.com/shownotes