Hide the 'cluster-wide access infrastructure' option when ChaosCenter is namespaced scope

[namkyu1999]

Litmus has two components, Chaos Center (control plane) and Chaos infrastructure (execution plane).

We can restrict Chaos Center's scope as cluster-wide or namespaced through passing env.
And we can also restrict Chaos infrastructure's scope as cluster-wide or namespaced through Chaos Center's UI.

The problem happened when we installed Chaos Center as namespaced and tried to install Chaos infrastructure as cluster-wide.
Because namespaced Chaos Center doesn't have permission to create the cluster-wide access chaos infrastructure, We have to disable cluster-wide access option.

Currently, We can face the error below

Anyone who want to take this issue, please let me know 😄

fyi

• docs
• slack

[Baalekshan]

hi @namkyu1999 , I would like to work on this.

[namkyu1999]

go ahead, @Baalekshan

[smitthakkar96]

What is the benefit of having the scope defined for ChaosCenter? Ideally, the control plane should be agnostic of what infra scope we use for the execution plane, know? Is the added complexity of restricting this worth it. Even if users can see the option to generate manifest they can only apply it if they have access to do so in cluster.

[Baalekshan]

I have setup litmus locally and how can i run this in a namespaced scope ? So that I could test it.

[jayesh9747]

@namkyu1999 @Baalekshan can i work on this or it is already sloved this issue .

[Baalekshan]

@jayesh9747 I have raised PR and it's on a pending review. @namkyu1999 can you take a look at my PR.