CI/CD with Kubernetes

Delivered at the Kubernetes San Antonio meetup. Overview of continuous integration & delivery platforms and how to use them with Kubernetes.

Transcript

1. CI/CD with Kubernetes Hart Hoover @hhoover
2. The opinions expressed in this talk are my own and not necessarily those of my employer
3. https://coreos.com/tectonic/
4. Agenda: The Hero’s Journey • The Ordinary World: You, before this meetup. • The Call to Adventure: Your invite to k8s SATX • Refusal of the Call: Meh, traffic. IDK if I want to go. Will there be food? • Meeting with the Mentor: Hi, that’s me. You are here. • Crossing the Threshold: You decide to stay, in spite of my slides.
5. The Hero’s Journey, cont. • Challenges and Temptations: I’ll say some controversial things, and discuss your options for CI/CD. Sort out your alliances and enemies here. What works for you? • The Ordeal: A LIVE DEMO! • The Reward: You overcome all doubts and gain knowledge on CI/CD
6. The Hero’s Journey, cont. • The Road Back: You take this knowledge back to your job/team. • The Resurrection: Your team will not want to change their ways, which may require some sacrifice, by you. By your action, the polarities in conflict at the beginning will be resolved. • The Master of Two Worlds: You now have the power to transform your company with your knowledge, as you yourself have been transformed.
7. A QUICK NOTE ON HOW BUSINESS WORKS
9. ALL CI/CD IS BASICALLY THE SAME
10. CI/CD IS NOT “DEVOPS”
15. Code
16. Code
17. The “Unit of Deployment”?
18. Code You have two jobs manifests
19. Code Your CI/CD system has two jobs manifests
20. Some opinions on Services vs. Self-Hosted
21. – Unknown “DevOps is YAML over SSH”
22. Some Options: Services
23. Cloud Provider Services
24. Cloud Provider Services .vsts-ci.yml Visual Studio Team Services
25. Cloud Provider Services .vsts-ci.yml Visual Studio Team Services CodeBuild CodePipeline Lambda(?)
26. Cloud Provider Services .vsts-ci.yml Visual Studio Team Services CodeBuild CodePipeline Lambda(?) Google Cloud Container Builder cloudbuild.yml
27. Cloud Provider Services .vsts-ci.yml Visual Studio Team Services CodeBuild CodePipeline Lambda(?) Google Cloud Container Builder cloudbuild.yml
28. Cloud Provider Services .vsts-ci.yml Visual Studio Team Services CodeBuild CodePipeline Lambda(?) Google Cloud Container Builder cloudbuild.yml
29. Cloud Provider Services .vsts-ci.yml Visual Studio Team Services CodeBuild CodePipeline Lambda(?) Google Cloud Container Builder cloudbuild.yml
30. Cloud Provider Services .vsts-ci.yml Visual Studio Team Services CodeBuild CodePipeline Lambda(?) Google Cloud Container Builder cloudbuild.yml AWS re:Invent - Nov 27
31. https://semaphoreci.com/community/tutorials/continuous-deployment-with-google-container-engine-and-kubernetes CUSTOM YAML FILES https://semaphoreci.com/docs/adding-custom- configuration-files.html
32. codeship-steps.yml https://documentation.codeship.com/pro/builds- and-configuration/steps/
33. http://docs.shippable.com/ci/yml-structure/ http://docs.shippable.com/platform/integration/ kubernetes/ shippable.yml
34. .travis.yml https://docs.travis-ci.com/user/getting-started/ NO OFFICIAL SUPPORT FOR KUBERNETES (OpenShift doesn’t count)
35. .circleci/config.yml https://circleci.com/docs/2.0/sample-config/ NO OFFICIAL SUPPORT FOR KUBERNETES (GKE doesn’t count)
36. Some Options: Self-Hosted
39. ¯\_(ツ)_/¯
40. DEPLOYMENT ONLY Depends on TravisCI or Jenkins for testing
41. DEPLOYMENT ONLY Only Kubernetes Manifests
42. https://draft.sh/
43. https://draft.sh/ FOR , NOT CI/CD
45. https://confluence.atlassian.com/bitbucket/ deploy-to-kubernetes-892623297.html bitbucket-pipelines.yml
47. DEMO TIME
48. Appendix: Multi-Stage Builds FROM golang:1.7.3 as builder WORKDIR /go/src/github.com/alexellis/href-counter/ RUN go get -d -v golang.org/x/net/html COPY app.go . RUN CGO_ENABLED=0 GOOS=linux go build -a -installsuffix cgo -o app . FROM alpine:latest RUN apk --no-cache add ca-certificates WORKDIR /root/ COPY --from=builder /go/src/github.com/alexellis/href-counter/app . CMD ["./app"] TINY IMAGES FTW
49. Hart Hoover @hhoover