Відео

Hi, how can we help?

Yes @FAISAL SK SABIT , you will need to pull the litmus component images first, retag and push to your private/local registry. In-case you are using helm, you will need to add the changes in values.yaml file before doing the helm install. github.com/litmuschaos/litmus-helm/tree/master/charts/litmus If you have any further queries/questions, feel free to ask them by joining the #litmus channel in Kubernetes slack. Details are given in the video description!

Thanks, Gabriel, feel free to join us on slack to stay connected!

Hi @Antony Johnson I Thanks for trying out LitmusChaos. I'm Amit from the LitmusChaos team. May I know the pre-defined workflow you used for testing? Currently we have 3 pre-defined workflows podtato-head, sock-shop and bank-of-anthos. Further, feel free to put forward any queries or concerns you have. You can also join the LitmusChaos Slack community to interact with the community members, contributors and maintainers. Slack details are available in the description section.

Can you please elaborate on the issue while trying to connect the ChaosHub? We will help you with an immediate resolution on getting started

​@@litmuschaos If the release was tested after a helm installation on any cluster, you could see the default 'Litmus ChaosHub Chartv/2.5.x' loads with an error when you click on the 'ChoasHubs' tab and this cannot be fixed no matter what we tried, therefore you can't even run an experiment ! How do you bypass this temporarily ?

@@litmuschaos The ChaosCharts cannot be loaded, it hangs in a pending state and times out with an error.

@@mediatwinkleTV We Would urge you to join the slack community to get immediate resolution on this? To join the slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

Hi Shweta, thanks for trying out Litmus! Would urge you to join the slack community to get immediate resolution on this? To join the slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

Hi @zukerberg007! The steps to run the experiment will be quite similar to the kubelet kill exp. Please follow the experiment docs v1-docs.litmuschaos.io/docs/docker-service-kill/ and give a try. To discuss more feel free to join our slack community. To join our slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

Hi @vamsi, Yes, we can create and submit the chaos-workflows in the same way as we do with argo-workflows as it uses argo-workflows internally. But if you want to integrate it with the portal to track the progress, monitor analytics, and other portal features then you need to create it from the portal itself. To discuss more feel to join our litmus slack community. To join our slack please follow the following steps: Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

Hi @vamsi, Yes, we can create chaos-workflows from argo-cli. But if you want to integrate it with the portal to track the progress, monitor analytics, and other portal features then you need to create it from the portal itself. The litmusctl(cli tool for litmus) can help here. It is in the alpha version right now. You will be able to manage your workflows with litmusctl in a couple of releases. To discuss more feel to join our litmus slack community. To join our slack please follow the following steps: Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

Hi @zukerberg007, If you're using aws ubuntu vm machine you can use the public ip and the port to access the frontend via NodePort service. For local you can use localhost. To discuss more feel to join our litmus slack community. You can put any questions you have. To join our slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

To join our slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

@@adarshkumar1237 Thank you

Thanks, Aksay! Hope you have started your journey with LitmusChaos already? Would love to know if you have any roadblocks or queries.

@@litmuschaos yeah, I have started!

@@akshayawate7239 Awesome Akshay! Looking forward to having you in our community for queries & info. To join our slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/ Looking forward to having you in our community!

does the experiment run for sometime and hog the cpu spike of pod or it fails immediately? would request you for logs of experiment pod which will be kubectl logs -f <experiment-name>-XXXX-XXXX -n <ns> . If is fails after chaos completion you have to change the CHAOS-KILL-COMMAND in pod-cpu-hog engine.yml Would request you to join us on slack to ask any queries you want. Will request you to share the logs there for immediate resolution. To join our slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

@@litmuschaos thank you. i got help from slack channel. answer is here: stackoverflow.com/questions/65225914/litmus-chaos-experiment-status-fail-step-failed-in-chaos-injection-phase

If we want to find the reason for failure then we have to check the logs of the chaos pod i.e, pod-io-stress-xxxx-xxxx. As of now, chaosresult is only able to tell the verdict pass/fail not the exact reason. from his example, we can suspect that it is a sample result(edited by him) because in describing output it is using *-pod-io-stress but in describe output `.name` is coming as * only.

Having said that, Keerthi we would love to invite you to our community for us to reach the depth of your problem and provide expert community solutions. To join our slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

you can use kubectl describe chaosresult

Hi Sunita. Thanks for choosing Litmus! Use kubectl describe chaosresult <name-of-chaos-result> -n <ns> and to get the name of the chaosresult use kubectl get chaosresult Currently, the chaosresult holds the details of what will happen during the chaos execution. Feel free to ask if you need further help. kubectl describe chaosresult <name-of-chaos-result> -n <ns> 2:26 and to get the name of chaosresult dokubectl get chaosresult

​@@aushafy Thanks for being of crucial help to our community. We would love to invite you to our slack community as well. To join our slack please follow the following steps! Step 1: Join the Kubernetes slack using the following link: slack.k8s.io/ Step 2: Join the #litmus channel on the Kubernetes slack or use this link after joining the Kubernetes slack: slack.litmuschaos.io/

Having said that Sunita do join us on slack to get your queries clarified immediately!

@@litmuschaos for sure. I have join to the slack community .. thank you