-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
28 additions
and
0 deletions.
There are no files selected for viewing
28 changes: 28 additions & 0 deletions
28
DevOps/Infrastructure-Solutions/Container/Podman/migrate-compose-to-kubefiles.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Migrate from podman-compose to Kubefiles | ||
|
||
## Overview | ||
|
||
Kubefiles are a way to define a podman pod and containers in a single file. They are similar to docker-compose files, | ||
but can also be used with Kubernetes. | ||
|
||
## Requirements | ||
|
||
The podman-compose or docker-compose file must be started with `podman-compose up -d` and the created podman pod should be listed with `podman pod ls`. | ||
|
||
## Generate Kubefiles | ||
|
||
### Pod | ||
|
||
Get the pod name via `podman pod ls` and generate the Kubefile with: | ||
|
||
```bash | ||
podman kube generate <pod_name> -f pod.kube.yaml | ||
``` | ||
|
||
### Persistent Volume Claim | ||
|
||
Get the volume name via `podman volume ls` and generate the Kubefile with: | ||
|
||
```bash | ||
podman kube generate <volume_name> -f pvc.kube.yaml | ||
``` |