Error during installation

[amitmindstix]

When I follow the instructions to run jmeter_cluster.sh, I get following errors -

error: unable to recognize "/home/amit/jmeter-kubernetes/jmeter_slaves_deploy.yaml": no matches for kind "Deployment" in version "apps/v1beta2"
service "jmeter-slaves-svc" created
Creating Jmeter Master
configmap "jmeter-load-test" created
error: unable to recognize "/home/amit/jmeter-kubernetes/jmeter_master_deploy.yaml": no matches for kind "Deployment" in version "apps/v1beta2"
Creating Influxdb and the service
configmap "influxdb-config" created
error: unable to recognize "/home/amit/jmeter-kubernetes/jmeter_influxdb_deploy.yaml": no matches for kind "Deployment" in version "apps/v1beta2"

[amitmindstix]

kubectl version

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.7", GitCommit:"8e1552342355496b62754e61ad5f802a0f3f1fa7", GitTreeState:"clean", BuildDate:"2017-09-28T23:56:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

[arashkaffamanesh]

the server version should be > 1.9.6 I think, we tested it on k8s 1.10.x and all works

[chandraiu]

Hi, I have kubectl version 1.17 but still see above error , i am trying to deploy it on AWS. Do we know the reason for this?

[chandraiu]

kubectl version

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.7", GitCommit:"8e1552342355496b62754e61ad5f802a0f3f1fa7", GitTreeState:"clean", BuildDate:"2017-09-28T23:56:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

@amitmindstix - How did you fix this?

[Mapreduce2]

I ran into this issue as well today with kubectl 1.17. I am not sure if the best solution but I had to modify at least the 4 meter-kubernetes/jmeter*_deploy.yaml files (mentioned in my error).

I had to change the apiVersion from apps/v1beta2 (or extensions/v1beta1) to use apps/v1 instead.

for x in ls jmeter-kubernetes/ | grep _deploy.yaml; do echo FILE:$x; cat jmeter-kubernetes/$x | head -2 ; done

FILE:jmeter_grafana_deploy.yaml apiVersion: apps/v1 kind: Deployment FILE:jmeter_influxdb_deploy.yaml apiVersion: apps/v1 kind: Deployment FILE:jmeter_master_deploy.yaml apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 kind: Deployment FILE:jmeter_slaves_deploy.yaml apiVersion: apps/v1 kind: Deployment

./jmeter_cluster_create.sh

_checking if kubectl is present Client Version: v1.17.0 Server Version: v1.17.0 Current list of namespaces on the kubernetes cluster: .... Creating Namespace: jmeterkubectl17test namespace/jmeterkubectl17test created Namspace jmeterkubectl17test has been created

Creating Jmeter slave nodes

Number of worker nodes on this cluster is 2

deployment.apps/jmeter-slaves created service/jmeter-slaves-svc created Creating Jmeter Master configmap/jmeter-load-test created deployment.apps/jmeter-master created Creating Influxdb and the service configmap/influxdb-config created deployment.apps/influxdb-jmeter created service/jmeter-influxdb created Creating Grafana Deployment deployment.apps/jmeter-grafana created service/jmeter-grafana created Printout Of the jmeterkubectl17test Objects

NAME READY STATUS RESTARTS AGE pod/influxdb-jmeter-694cd55c9c-vpbnl 0/1 ContainerCreating 0 1s pod/jmeter-grafana-64575d9586-5jzq9 0/1 ContainerCreating 0 0s pod/jmeter-master-855fdd69f-66dt8 0/1 ContainerCreating 0 1s pod/jmeter-slaves-7dc78c4984-jgfjk 0/1 ContainerCreating 0 2s pod/jmeter-slaves-7dc78c4984-zrc9t 0/1 ContainerCreating 0 2s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/jmeter-grafana NodePort 10.96.71.191 3000:31823/TCP 0s service/jmeter-influxdb ClusterIP 10.96.40.220 8083/TCP,8086/TCP,2003/TCP 1s service/jmeter-slaves-svc ClusterIP None 1099/TCP,50000/TCP 2s

NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/influxdb-jmeter 0/1 1 0 1s deployment.apps/jmeter-grafana 0/1 1 0 0s deployment.apps/jmeter-master 0/1 1 0 1s deployment.apps/jmeter-slaves 0/2 2 0 2s

NAME DESIRED CURRENT READY AGE replicaset.apps/influxdb-jmeter-694cd55c9c 1 1 0 1s replicaset.apps/jmeter-grafana-64575d9586 1 1 0 0s replicaset.apps/jmeter-master-855fdd69f 1 1 0 1s replicaset.apps/jmeter-slaves-7dc78c4984 2 2 0 2s [blruss@TRCv010 jmeter-kubernetes]$_

Is this a valid workaround/fix?

[arashkaffamanesh]

nice, thanks, we'll have a look into it .