From the course: Kubernetes: Your First Project
Unlock this course with a free trial
Join today to access over 25,300 courses taught by industry experts.
Why Helm? - Kubernetes Tutorial
From the course: Kubernetes: Your First Project
Why Helm?
- [Instructor] We've successfully gotten Explore California up and running on Kubernetes. We've even enabled HTTPS for the website without having to change the application at all. All of this is very exciting. Unfortunately, maintaining Explore California in its current state will be a guaranteed headache. Earlier, we learned that every resource in Kubernetes can be represented as YAML. This slide shows the YAML for our Explore California deployment. We use kubectl create deployment to create this deployment. However, recall that we had to use kubectl edits to modify this deployment's image pull policy to work around limitations with images loaded into kind clusters. We would have to use kubectl edit every time we wanted to change something with Explore California's deployment, service, or ingress. Some resources, like Loose Pods, have many properties that can't be changed this way. In these situations, you'll need to use kubectl get to save the YAML file, make your changes, delete…
Contents
-
-
-
-
-
-
-
(Locked)
Why Helm?2m 14s
-
(Locked)
Initializing your chart4m 45s
-
(Locked)
Templatizing the deployment8m 57s
-
(Locked)
Testing your templates2m 16s
-
(Locked)
Templatizing the service and ingress7m 27s
-
(Locked)
Templatizing the cert-manager issuer2m 22s
-
(Locked)
Deploying your Helm chart7m 40s
-
(Locked)
Challenge: Explore California sale1m 29s
-
(Locked)
Solution: Explore California sale8m 4s
-
(Locked)
-
-
-