Clicking on container name in details sidecar should add -c to logs command

[mark-nc]

Describe the bug
Clicking on the container name in the details sidecar for a pod runs the logs command agaist the pod and container name but does not include the -c flag in front of the container name. This can fail if the pod contains more than one container. In the case of one container, this is tolerated by kubectl even though kubectl logs --help calls out use of -c, but if using the Red Hat OpenShift Container Platform equivalent CLI oc it will always fail because oc enforces the syntax of putting -c before the container name.

Steps to reproduce the behavior

1. Run kubectl get pods -n <someNamespace>
2. Click on a pod in the table
3. Go to the Containers tab in the pod details sidecar
4. Click on the container name
5. Observe that the resulting command executed is kubectl logs <podName> <containerName> -n <someNamespace> (no -c in front of <containerName>)

Expected behavior
The command should always work and will always work if the -c flag is always included before the container name as specified in the help documentation.

System

• Kui version: 6.0.21 and plugin-kubeui 1.0.16 (but may also still exist in 8.x)
• Operating system: Red Hat UBI8 container (effectively RHEL 8)

[mark-nc]

New information.... oc v4.4 behaves the same as kubectl and does not require the -c flag in front of the container name if there is only one container, but it still makes sense to include it on any logs command for the container as including -c always works in all cases.