Has anyone tried to deploy this on OpenShift?

[alberttwong]

Just curious.....

[osmancis]

I did and it works great.

[romancin]

I have been testing this, and kube-mokey container runs well in OpenShift, but it doesn't work with OpenShift deploymentConfig, only with kubernetes deployments. If you use kubernetes deployments, you loose the ability to use image streams, lifecycle hooks and custom deployment strategies, as stated in this document:
https://docs.openshift.com/container-platform/3.11/dev_guide/deployments/kubernetes_deployments.html#dev-guide-kubernetes-deployments-support

[alberttwong]

@romancin How are you starting or loading the container in OCP?

[romancin]

I am running kube-monkey inside Openshift. If I use Kubernetes Deployments inside Openshift, kube-monkey works fine. But if you use Openshift DeploymentConfig (this is the standard mode for Openshift), kube-monkey doesn’t work.

…

El 11 ene 2019, a las 19:59, Albert Wong ***@***.***> escribió: @romancin How are you starting or loading the container in OCP? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[alberttwong]

Can you share what you did? I take it that you're loading via yaml. I can look at why since I'm a Red Hatter that works on OCP.

[osmancis]

@romancin Can you make sure you defined the config map? I missed it first time I ran this K Monkey

[alberttwong]

For the issue,

error: couldn't get deployment kube-monkey-5: replicationcontrollers "kube-monkey-5" is forbidden: User "system:serviceaccount:kube-system:deployer" cannot get replicationcontrollers in the namespace "kube-system": User "system:serviceaccount:kube-system:deployer" cannot get replicationcontrollers in project "kube-system" 

oc -n kube-system adm policy add-role-to-user -z deployer system:deployer
oc -n kube-system adm policy add-role-to-user -z builder system:image-builder
oc -n kube-system adm policy add-role-to-group system:image-puller system:serviceaccounts:kube-system

[alberttwong]

Answer

git clone https://github.com/asobti/kube-monkey.git
cd examples
oc login http://someserver/ -u system:admin
oc project kube-system
oc create -f configmap.yaml
oc -n kube-system adm policy add-role-to-user -z deployer system:deployer
oc -n kube-system adm policy add-role-to-user -z builder system:image-builder
oc -n kube-system adm policy add-role-to-group system:image-puller system:serviceaccounts:kube-system
oc run kube-monkey --image=docker.io/ayushsobti/kube-monkey:v0.3.0 --command -- /kube-monkey -v=5 -log_dir=/var/log/kube-monkey
oc volume dc/kube-monkey --add --name=kubeconfigmap -m /etc/kube-monkey -t configmap --configmap-name=kube-monkey-config-map

[asobti]

Fixed by #137

[alberttwong]

FYI.. this is another effort. https://github.com/chaitanyaenr/kraken

[romancin]

Sorry, but that is not the problem, as I said, kube-monkey is working well. The problem is that kube-monkey is searching for Deployments using the kubernetes api. When you use Openshift DeploymentConfig, kubernetes Deployments are not used, so kube-monkey thinks that it doesn’t have any pods to kill. If you do a `kubectl get deployments` on a Openshift cluster when you are using DeploymentConfigs, the output is empty.

…

El 11 ene 2019, a las 22:54, Ayush Sobti ***@***.***> escribió: Fixed by #137 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[romancin]

This seems to make chaos only on the Openshift infrasctucture and not in the application pods, so I think the purpose is different than kube-monkey. Both working together would be awesome 🙂

…

El 11 ene 2019, a las 23:01, Albert Wong ***@***.***> escribió: FYI.. this is another effort. https://github.com/chaitanyaenr/kraken — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[alberttwong]

Sorry, but that is not the problem, as I said, kube-monkey is working well. The problem is that kube-monkey is searching for Deployments using the kubernetes api. When you use Openshift DeploymentConfig, kubernetes Deployments are not used, so kube-monkey thinks that it doesn’t have any pods to kill. If you do a kubectl get deployments on a Openshift cluster when you are using DeploymentConfigs, the output is empty.

So I miss understood. I thought you couldn't deploy kube-monkey in a DC configuration. Unfortunately you'd have to rewrite kube-monkey so that it understood OCP DC.

[loveshjain]

@alberttwong I deployed the kube-monkey like you mention on my openshift, but it does not seems to be working. Its giving me

I0531 04:04:08.061773 1 schedule.go:57] Status Update: 0 terminations scheduled today

When I did kubectl get deployments i got No resources found.

Any idea?