- he file defines various aspects of your application deployment, including:
- Container image to use
- Number of replicas (pods) to run
- Resource requests and limits for CPU and memory
- Environment variables for your application
- Port mappings for containerized applications
- Volume mounts for persistent storage
- Network configurations (optional)
- Security configurations (optional)
Benefits of Using Manifest Files:
- Declarative: They specify the desired state, and the Kubernetes API server works to achieve that state. This simplifies deployment management.
- Version Control: You can version control your manifest files alongside your application code, ensuring consistency and reproducibility of your deployments across environments.
- Reusability: Well-defined manifest files can be reused for deployments of the same application or similar applications.
- Portability: Manifest files can be portable across different Kubernetes or OpenShift clusters if they adhere to the same API versions.
Additional Manifest File Types:
There can be multiple manifest files for a single application deployment, defining different Kubernetes or OpenShift resources:
- Deployment: Defines how pods are created and managed.
- Service: Exposes an application running on pods as a network service.
- PersistentVolumeClaim: Requests storage for your application's data.
- ConfigMap/Secret: Stores configuration data or sensitive information for your application.
