Okteto devflow docs appear to be missing some detail needed about litmus-go HOT 7 CLOSED

Just to confirm no CHAOSENGINE env var set:

litmus:litmus-experiment okteto> env | grep CHAOS
CHAOS_NAMESPACE=litmus
TOTAL_CHAOS_DURATION=300
CHAOS_SERVICE_ACCOUNT=scheduler

from litmus-go.

Suppose needs a fix. Hope to get back on this soon!

from litmus-go.

Hi @damienomurchu - thanks for using the dev guide (we also have some context here, if you'd like - a bit stale but the theory holds).

The idea with Okteto is to provide a dev environment in the cluster. We are launching a dummy/test deployment (test.yaml) with all the actual experiment dependencies built-in (ENVs, configmaps, secrets etc.,) - with the test image being replaced by the okteto dev container upon doing okteto up - from which the experiment can be launched via the commands (followed by code-changes/re-run until expected behavior)

At this point we can actually go ahead w/ the PR on litmus-go repository.

Having said that the next steps (which will aid in the experiment being shown up on the chaoshub and provide more validation are provided below:

• create chaosexperiment CR (generated as part of the litmus-sdk command / but can be constructed based on other examples)
• construct/use the rbac (you might have this already from the devtest period using okteto) for providing it in the .spec.chaosServiceAccount in the chaosengine.
• create chaosengine CR (needs to be manually constructed, again based on other examples).

Once these artifacts are available you can create the chaosengine resource in the desired ns to launch chaos-runner and az-experiment pod (which injects the chaos)

from litmus-go.

Thanks @ksatchit - that's great, will review what you added and linked 👍

from litmus-go.

Thanks. Having said that -- we should ideally not see FATAL[2020-12-08T16:01:12Z] Unable to initialise probes details from chaosengine, err: Unable to Get the chaosengine, err: resource name may not be empty exit status 1 -- when doing the go run experiment.go step. (unless you have a CHAOSENGINE env).

cc: @ispeakc0de thoughts?

from litmus-go.

Suppose needs a fix. Hope to get back on this soon!

Thanks @ispeakc0de & @ksatchit for the fix!

I had been working around it by disabling the error checking around the probe and chaosengine, but will rebase against the latest master now its been patched 👍

from litmus-go.

Fixed by #235

Has been added to scaffold: #237

from litmus-go.