Missing Batch debug-file configmap about spm-kubernetes

[andreyzher]

Glad that unblocked the batch pods for you - a fix will be included in the next release.

Please keep in mind the Kubernetes version skew policy
The client must be within 1 minor version of the kube-apiserver, so you need to upgrade your kubectl to a version in the 1.15.x - 1.17.x range.
Additionally, Kubernetes only supports the last 3 versions - currently the latest version of Kubernetes is 1.18.x, so while 1.16.x is still supported, it is nearing deprecation. Amazon EKS might give you a little more time, but I recommend making plans to upgrade your cluster(s).

Any time we attempted to operate outside this policy, a variety of unpredictable issues arose - I find it's best to keep the client and server versions the same (and within the supported range), whenever possible.

[andreyzher]

Hi,

Thanks for raising this.
Could you please provide the output of kubectl version and oc version ?

Oddly, that error doesn't come up for me in IKS or OCP, despite the fact that I see the volume definition, and there definitely not being a debug ConfigMap in the namespace.

As a local fix/workaround, you may remove the 3 lines you highlighted - these seem to have been leftover / incorrectly copy & pasted from another activity.

[meathead23]

Hey @andreyzher

Here's the output from our kubectl version

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.8-eks-fd1ea7", GitCommit:"fd1ea7c64d0e3ccbf04b124431c659f65330562a", GitTreeState:"clean", BuildDate:"2020-05-28T19:06:00Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

I'm removed the 3 lines and the batch pod now seems to be running.

Thanks