From 69d7407afbe76eb7553b84193f93281b9c5ce904 Mon Sep 17 00:00:00 2001 From: Niall Crowe Date: Wed, 27 Jul 2022 23:16:57 +0100 Subject: switch from "kube/play" endpoint to "play/kube" endpoint. When podman kube play was added the endpoint for the kube play/play kube commands was switched from the "play kube" endpoint to the new "kube play" endpoint. This caused issues with the remote client, requiring the need to use the "play kube" endpoint again in order to avoid these issues. Signed-off-by: Niall Crowe --- cmd/podman/kube/play.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'cmd/podman') diff --git a/cmd/podman/kube/play.go b/cmd/podman/kube/play.go index 685cb521c..6e0050cbf 100644 --- a/cmd/podman/kube/play.go +++ b/cmd/podman/kube/play.go @@ -164,7 +164,7 @@ func playFlags(cmd *cobra.Command) { _ = cmd.RegisterFlagCompletionFunc(contextDirFlagName, completion.AutocompleteDefault) // NOTE: The service-container flag is marked as hidden as it - // is purely designed for running kube-play in systemd units. + // is purely designed for running kube-play or play-kube in systemd units. // It is not something users should need to know or care about. // // Having a flag rather than an env variable is cleaner. -- cgit v1.2.3-54-g00ecf