mirror of https://github.com/containers/podman.git
a7fc8a1460
If you run `podman play kube` on a yaml file that only contains configMaps, podman will fail with the error: Error: YAML document does not contain any supported kube kind This is not strictly true; configMaps are a supported kube kind. The problem is that configMaps aren't a standalone entity. They have to be used in a container somewhere, otherwise they don't do anything. This change adds a new message in the case when there only configMaps resources. It would be helpful if podman reported which configMaps are unused on every invocation of kube play. However, even if that feedback were added, this new error messages still helpfully explains the reason that podman is not creating any resources. [NO NEW TESTS NEEDED] Signed-off-by: Jordan Christiansen <xordspar0@gmail.com> |
||
|---|---|---|
| .. | ||
| annotations | ||
| api | ||
| auth | ||
| autoupdate | ||
| bindings | ||
| channel | ||
| checkpoint | ||
| copy | ||
| criu | ||
| ctime | ||
| domain | ||
| env | ||
| errorhandling | ||
| hooks | ||
| inspect | ||
| kubeutils | ||
| lookup | ||
| machine | ||
| namespaces | ||
| parallel | ||
| ps | ||
| resolvconf | ||
| rootless | ||
| rootlessport | ||
| seccomp | ||
| selinux | ||
| servicereaper | ||
| signal | ||
| specgen | ||
| specgenutil | ||
| systemd | ||
| terminal | ||
| timetype | ||
| trust | ||
| util | ||