Joe Talerico (rook)

> Yes. It requires an update in the fork with latest mainstream changes and then a merge of it in the PR's branch. It resolved the issue for Vicente's [PR](https://github.com/cloud-bulldozer/e2e-benchmarking/pull/682#issuecomment-1966848167)....

/test e2e-cluster-density-v2-single-node

@mrbojangles3 also, the DCO bot will complain until you sign your commits.

> w.r.t the code that is brought in from the copy/paste. I was thinking that we might need it in the future and we would rather having hanging around unused...

> Looking to check my understanding here. We are thinking it would be best to move the whereabouts testing to be completely inside of kube-burner-ocp, then just calling it as...

I recently bumped into this with a GKE cluster. sysdump attached. I used the cli to install. Kernel is 5.10, using the GKE COS. [cilium-sysdump-20220221-132742.zip](https://github.com/cilium/cilium-service-mesh-beta/files/8111483/cilium-sysdump-20220221-132742.zip)

I swapped my GKE cluster from COS to Ubuntu and have made progress.

Just hit this issue on EKS ``` /¯¯\ /¯¯\__/¯¯\ Cilium: 4 errors \__/¯¯\__/ Operator: 1 errors /¯¯\__/¯¯\ Hubble: disabled \__/¯¯\__/ ClusterMesh: disabled \__/ DaemonSet cilium Desired: 2, Ready: 2/2, Available:...

`The Deployment "kepler-operator-controller" is invalid: spec.template.spec.containers[0].volumeMounts[0].name: Not found: "cert"`

@vprashar2929 so, `make fresh` seems to deploy a kind cluster? I am trying to use `make deploy` install on a existing cluster?