Skip to content

Kube Quadlet should support multiple YAML #26274

@axel7083

Description

@axel7083

Feature request description

When dealing with medium application, with several containers, PVC, configmap etc. we may want to split out YAML into smaller chunk.

Since #9129 podman kube play support resources separated by --- in a single YAML, but this prevent us from providing multiple files, each containing multiple resources.

Suggest potential solution

In #9129 (comment) @mheon suggested that the podman kube play command support multiple file as argument like podman play kube pod1.yaml pod2.yaml.

This could allow us to define multiple Yaml property in the kube quadlet , as this is the ExecStart generated currently

ExecStart=/usr/bin/podman kube play --replace --service-container=true <yaml-file>

If the podman kube play command support multiple file, we can easily just add those files to the list in the ExecStart command.

For implementation details, as podman already support providing multiple resources, the client can just concatenate all the resources in one file and send it to the backend.

Have you considered any alternatives?

Concatenate files manually

Additional context

Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    jirakind/featureCategorizes issue or PR as related to a new feature.triagedIssue has been triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions