From the course: Automating Kubernetes with GitOps
Unlock this course with a free trial
Join today to access over 24,700 courses taught by industry experts.
Kubernetes storage - Kubernetes Tutorial
From the course: Automating Kubernetes with GitOps
Kubernetes storage
- So your applications will also need access to storage. By nature container storage is ephemeral. That means you remove the container. All files you created in it are gone unless you've taken your measures to provide some persistent storage. In Kubernetes, bots may be configured with volumes as persistent storage, and these volumes can directly defer to different types of external storage. That's a pod volume. And as an alternative to the pod volume, you can also use persistent volumes. And the persistent volumes can be used as dedicated objects to point to the specific storage. Pods can then be configured with a persistent volume claim. And using persistent volume claims allows for an increased level of flexibility. In a GitOps environment, using PVCs is recommended as it allows you to create specific persistent volumes for each environment and point to these persistent volumes in a very flexible way so that if your application is in the QA states, it'll have access to different…
Contents
-
-
-
-
-
-
-
-
-
-
(Locked)
Learning objectives41s
-
(Locked)
Using namespaces to represent GitOps environments1m 38s
-
(Locked)
Labels and annotations5m 57s
-
(Locked)
Using ConfigMaps to provide application data3m 58s
-
(Locked)
Kubernetes storage9m 7s
-
(Locked)
Using services1m 34s
-
(Locked)
Using Ingress9m 12s
-
(Locked)
Ingress access to services in specific namespaces5m 24s
-
(Locked)
Using NetworkPolicy to isolate GitOps environments6m 56s
-
(Locked)
-
-
-
-
-
-
-
-
-
-