Feature request description

Summary

When a Deployment manifest specifies replicas: N, podman play kube should honor that and create N pods—rather than silently limiting it to one.

Motivation & References

• As of Podman 4.4, pods created via play kube are capped at one replica: “limits the replica count to 1”.
• Issue #16765 describes pod startup failures due to port binding conflicts when attempting duplicates.
• PR #16766 introduces random port assignment to mitigate such conflicts.
• PR #17082 warns users when attempting multi‑replica deployment with play kube.
• GitHub Issue (upstream): https://github.com/containers/podman/issues/26769

Proposal

• Allow play kube to create multiple pods when spec.replicas > 1.
• Handle port conflicts gracefully—e.g., through randomized host ports or offset mapping.
• Maintain or improve user feedback: explicitly warn if scaling isn't feasible.
• Add example use cases or tests in CI/docs to demonstrate correct behavior.

Benefits

Better aligns podman play kube with real‑world Kubernetes workflows and streamlines local/demo usage—reducing manual steps and improving reliability.

Thank you for considering this feature!