chaos-mesh: Failed to apply PodChaos

Bug Report

What version of Kubernetes are you using?

Client Version: version.Info{Major:“1”, Minor:“12”, GitVersion:“v1.12.10”, GitCommit:“e3c134023df5dea457638b614ee17ef234dc34a6”, GitTreeState:“clean”, BuildDate:“2019-07-08T03:50:59Z”, GoVersion:“go1.10.8”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“11+”, GitVersion:“v1.11.6-45+c49c6cc7ec3af7”, GitCommit:“c49c6cc7ec3af777e580543db675b2d54533afaf”, GitTreeState:“clean”, BuildDate:“2019-03-20T07:45:02Z”, GoVersion:“go1.10.3”, Compiler:“gc”, Platform:“linux/amd64”}

What did you do?

kubectl apply -f pod-failure.yaml

pod-failure.yaml as below apiVersion: pingcap.com/v1alpha1 kind: PodChaos metadata: name: pod-failure namespace: chaos-testing spec: action: pod-failure # the specific chaos action to inject; supported actions: pod-kill/pod-failure mode: one # the mode to run chaos action; supported modes are one/all/fixed/fixed-percent/random-max-percent duration: “60s” # duration for the injected chaos experiment selector: # pods where to inject chaos actions namespaces: - default # the namespace of the system under test (SUT) you’ve deployed labelSelectors: “app.kubernetes.io/component”: “pd” # the label of the pod for chaos injection scheduler: # scheduler rules for the running time of the chaos experiments about pods. cron: “@every 5m”

What did you expect to see? PodChaos injects chaos into tidb pods.

What did you see instead? Error from server (InternalError): error when creating “pod-failure.yaml”: Internal error occurred: failed calling admission webhook “mpodchaos.kb.io”: Post https://chaos-mesh-controller-manager.default.svc:443/mutate-pingcap-com-v1alpha1-podchaos?timeout=30s: dial tcp 10.163.255.71:443: connect: connection refused

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 17 (9 by maintainers)

Most upvoted comments

“no route to host” is caused by an calico error in my k8s env. It works with hostNetwork.