You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a MPI job is being started a launcher and multiple worker pods are being created. The launcher then connects to the workers using kubectl exec. The kubectl version used is pretty old. It looks like a kubectl cli in version 1.15 is being used.
If sidecar containers are being used, the chances are high that the launcher then connects to the sidecar container instead to the actual worker container. This can be mitigated by setting an annotation kubectl.kubernetes.io/default-container. This annotation can only be correctly interpreted by a kubectl in a version >= 1.21.
So what is needed is an updated kubectl in the MPI launcher pod. Kubectl seems to be installed by an init container named "kubectl-delivery". It uses the following image: mpioperator/kubectl-delivery:latest. That image should be rebuilt using a new version of kubectl, so there is no problem with multiple containers in the MPI worker pods.
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
When a MPI job is being started a launcher and multiple worker pods are being created. The launcher then connects to the workers using
kubectl exec
. The kubectl version used is pretty old. It looks like a kubectl cli in version 1.15 is being used.If sidecar containers are being used, the chances are high that the launcher then connects to the sidecar container instead to the actual worker container. This can be mitigated by setting an annotation
kubectl.kubernetes.io/default-container
. This annotation can only be correctly interpreted by a kubectl in a version >= 1.21.So what is needed is an updated kubectl in the MPI launcher pod. Kubectl seems to be installed by an init container named "kubectl-delivery". It uses the following image:
mpioperator/kubectl-delivery:latest
. That image should be rebuilt using a new version of kubectl, so there is no problem with multiple containers in the MPI worker pods.The text was updated successfully, but these errors were encountered: