Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

podman kube play reads only the first entity in the configmap files passed with --configmap #18537

Closed
ygalblum opened this issue May 11, 2023 · 0 comments · Fixed by #18538
Closed
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. kube locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@ygalblum
Copy link
Contributor

Issue Description

When using podman kube play the caller may pass an additional file that includes config maps though the --configmap parameter. When this parameter is passed, podman reads and processes only the first entity in the file. However, a YAML file may include multiple sections. As a result, users cannot hold multiple configmaps in one file.

Steps to reproduce the issue

Steps to reproduce the issue

  1. Create a configmap.yaml file with two configmap sections
  2. Create a pod.yaml file in which the pod references the second configmap in the configmap.yaml file
  3. Run podman kube play --configmap=./config-map.yaml pod.yaml

Describe the results you received

Error: cannot set env : configmap not found

Describe the results you expected

Podman should read the entire configmap file and extract all the entities inside it.

podman info output

If you are unable to run podman info for any reason, please provide the podman version, operating system and its version and the architecture you are running.

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@ygalblum ygalblum added the kind/bug Categorizes issue or PR as related to a bug. label May 11, 2023
@vrothberg vrothberg added the kube label May 11, 2023
@ygalblum ygalblum self-assigned this May 11, 2023
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. kube locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants