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
I installed helm and ChaosBlade Operator. Then I checked it works on "create k8s node-cpu" experiment. But when I tried "create k8s pod-network delay" experiment using the follow yaml, and the kubectl apply -f command,
However, when I tried the "create k8s container-network delay" experiment for the same pod (the pod has only one container), it was success.
This problem aslo exist on the other pod.
Describe what you expected to happen
It is expected to inject network delay successfully.
How to reproduce it (as minimally and precisely as possible)
Create the yaml file as mentioned above.
use kubectl create -f xxx.yaml to create the experiment.
use kubectl get blade delay-pod-network-by-names -o json to see the result.
related ot #232.
it's a bug of operator. in "create k8s pod-network delay" case, the operator find the containerId from the chaosblade-tool-9462j,rather than you assigned.
Issue Description
Bug report
Describe what happened (or what feature you want)
I installed helm and ChaosBlade Operator. Then I checked it works on "create k8s node-cpu" experiment. But when I tried "create k8s pod-network delay" experiment using the follow yaml, and the
kubectl apply -f
command,I got the following result (a part of the whole result) when using
kubectl get blade delay-pod-network-by-names -o json
command.The network info for the pod is as following:
However, when I tried the "create k8s container-network delay" experiment for the same pod (the pod has only one container), it was success.
This problem aslo exist on the other pod.
Describe what you expected to happen
It is expected to inject network delay successfully.
How to reproduce it (as minimally and precisely as possible)
kubectl create -f xxx.yaml
to create the experiment.kubectl get blade delay-pod-network-by-names -o json
to see the result.Tell us your environment
chaosblade version
Anything else we need to know?
The text was updated successfully, but these errors were encountered: