Is kubectl-fdb version must be the same with apple operator version?

Using FoundationDB Kubernetes Operator
1

For example, my apple operator is on 0.48.0, could it work with kubectl-fdb v1.2?
For now, I got the below error:

{"command":"/usr/local/bin/kubectl","args":"[/usr/local/bin/kubectl fdb fix-coordinator-ips -c mdm-foundationdb-ibm -n testoperator1]","fdbcluster":"testoperator1/mdm-foundationdb-ibm","name":"controllers.fdbcontroller.FdbCluster","timestamp":"2022-05-16T14:51:48.336Z","message":"Running command"}
{"output":"","fdbcluster":"testoperator1/mdm-foundationdb-ibm","name":"controllers.fdbcontroller.FdbCluster","timestamp":"2022-05-16T14:51:48.372Z","message":"Command output"}
{"output":"Error: exec format error
","fdbcluster":"testoperator1/mdm-foundationdb-ibm","name":"controllers.fdbcontroller.FdbCluster","timestamp":"2022-05-16T14:51:48.372Z","message":"Command stderr"}

Kindly share some insights. thank you.

2

The kubectl fdb plugin 1.+ should only be used with the operator 1.+ version in your case you should make use of an older version of the kubectl fdb plugin. The v0.51.1 version of the kubectl fdb plugin would be the last version that supports versions below 1.+ Release Release v0.51.1 · FoundationDB/fdb-kubernetes-operator · GitHub. In general the plugin should work for the same major releases but I would suggest to keep the operator and kubectl fdb plugin the same or at least close.

3

Thank you @johscheuer

4

But the provided error Error: exec format error is probably unrelated to the version of the kubectl fdb plugin and you should check if you actually downloaded the correct binary for the plugin (correct OS + architecture).

5

It sounds like it’s the version issue though, I tried the same 0.48.0 version of kubectl-fdb, and it works without this issue.