You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everybody,
I am trying to use chaos monkey but I have an issue that I cannot solve. I have deployed Spinnaker at EKS in AWS successfully and then created an application that deploys 3 pods in that kubernetes cluster. I am also successfully deploying chaos monkey in a standalone EC2 and I can connect it to the Spinnaker application and also retrieve some information. For example:
chaosmonkey regions spinnaker eks-spinnaker:
spinnaker
The problem is that I cannot retrieve the instances and of course not terminate it:
chaosmonkey eligible spinnaker eks-spinnaker:
unexpected response code (404) from http://10.176.14.154:31994/applications/spinnaker/clusters/eks-spinnaker/spinnaker/kubernetes/spinnaker/serverGroups/target/CURRENT?onlyEnabled=true
It looks like that chaos monkey requests an url that doesnt exist.
Is it anyone that could help me a bit with that?
The text was updated successfully, but these errors were encountered:
Hello everybody,
I am trying to use chaos monkey but I have an issue that I cannot solve. I have deployed Spinnaker at EKS in AWS successfully and then created an application that deploys 3 pods in that kubernetes cluster. I am also successfully deploying chaos monkey in a standalone EC2 and I can connect it to the Spinnaker application and also retrieve some information. For example:
chaosmonkey regions spinnaker eks-spinnaker:
spinnaker
The problem is that I cannot retrieve the instances and of course not terminate it:
chaosmonkey eligible spinnaker eks-spinnaker:
unexpected response code (404) from http://10.176.14.154:31994/applications/spinnaker/clusters/eks-spinnaker/spinnaker/kubernetes/spinnaker/serverGroups/target/CURRENT?onlyEnabled=true
It looks like that chaos monkey requests an url that doesnt exist.
Is it anyone that could help me a bit with that?
The text was updated successfully, but these errors were encountered: