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.
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
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
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