You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the entry page of the project I got the impression that Zarf can be used to package generic software for air-gap scenarios, because K8s is not being mentioned anywhere in that page. Although it is clear to me, that the main focus is packaging K8s applications, I wonder it it can be used for other container-centric types of software.
What I am interested on is somehow packaging a docker-compose setup: docker-compose.yaml configuration file + corresponding container images.
If these non-mainstream types of packages are considered, then the documentation should be improved to announce it prominently enough. It is only for K8s applications, then probably the entry page should mention that to avoid frustration of potential users.
The text was updated successfully, but these errors were encountered:
Looking at the entry page of the project I got the impression that Zarf can be used to package generic software for air-gap scenarios, because K8s is not being mentioned anywhere in that page. Although it is clear to me, that the main focus is packaging K8s applications, I wonder it it can be used for other container-centric types of software.
What I am interested on is somehow packaging a docker-compose setup:
docker-compose.yaml
configuration file + corresponding container images.If these non-mainstream types of packages are considered, then the documentation should be improved to announce it prominently enough. It is only for K8s applications, then probably the entry page should mention that to avoid frustration of potential users.
The text was updated successfully, but these errors were encountered: