How to Configure a Pod to Use a Volume for Storage on Kubernetes K8s or OpenShift OCP? I’m going to show you a live Playbook and some simple Ansible code. I’m Luca Berton and welcome to today’s episode of Ansible Pilot. A Container's file system lives only as long as the Container does. So when a Container terminates and restarts, filesystem changes are lost. For more consistent storage that is independent of the Container, you can use a Volume. This is especially important for stateful applications, such as key-value stores (such as Redis) and databases. Ansible creates Kubernetes or OpenShift service - `kubernetes.core.k8s` - Manage Kubernetes (K8s) objects Let's talk about the Ansible module `k8s`. The full name is `kubernetes.core.k8s`, which means that is part of the collection of modules of Ansible to interact with Kubernetes and Red Hat OpenShift clusters. It manages Kubernetes (K8s) objects. Parameters - name _string_ /namespace _string_ - object name / namespace - api_version _string_ - "v1" - kind _string_ - object model - state _string_ - present/absent/patched - definition _string_ - YAML definition - src _path_ - path for YAML definition - template _raw_ - YAML template definition - validate _dictionary_ - validate resource definition There is a long list of parameters of the `k8s` module. Let me summarize the most used. Most of the parameters are very generic and allow you to combine them for many use-cases. The `name` and `namespace` specify object name and/or the object namespace. They are useful to create, delete, or discover an object without providing a full resource definition. The `api_version` parameter specifies the Kubernetes API version, the default is "v1" for version 1. The `kind` parameter specifies an object model. The `state` like for other modules determines if an object should be created - `present` option, patched - `patched` option, or deleted - `absent` option. The `definition` parameter allows you to provide a valid YAML definition (string, list, or dict) for an object when creating or updating. If you prefer to specify a file for the YAML definition, the `src` parameter provides a path to a file containing a valid YAML definition of an object or objects to be created or updated. You could also specify a YAML definition template with the `template` parameter. You might find useful also the `validate` parameter in order to define how to validate the resource definition against the Kubernetes schema. Please note that requires the `kubernetes-validate` python module. Links - [kubernetes.core.k8s](https://docs.ansible.com/ansible/latest/collections/kubernetes/core/k8s_module.html) - [Configure a Pod to Use a Volume for Storage](https://kubernetes.io/docs/tasks/configure-pod-container/configure-volume-storage/) - [redis image](https://hub.docker.com/_/redis) ## Playbook How to Configure a Pod to Use a Volume for Storage on Kubernetes K8s or OpenShift OCP with Ansible Playbook. I’m going to create a Pod