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
We want to use kurtosis in k8s cluster, shared across multiple developers. For this we want to use isolated namespaces per team/use-case so that we could manage the respective resources separately.
However, presently kurtosis would generate the namespace name for k8s automatically and use pattern kurtosis-engine-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, which makes it impossible to tell by the namespace name which is which.
It would be great if the namespace to use would be configurable with a CLI parameter. The present behaviour could stay as-is for the default (no CLI provided) cases.
Also, if kurtosis would detect more than 1 running engine (in more than 1 namespace), it could fail with a message to specify the desired engine via CLI.
How important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered:
Background & motivation
We want to use
kurtosis
in k8s cluster, shared across multiple developers. For this we want to use isolated namespaces per team/use-case so that we could manage the respective resources separately.However, presently
kurtosis
would generate thenamespace
name for k8s automatically and use patternkurtosis-engine-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
, which makes it impossible to tell by the namespace name which is which.At the same time, it would fail if it detects more than one engine running in a particular cluster, which makes it impossible to even use more than 1 namespace to begin with.
Desired behaviour
It would be great if the namespace to use would be configurable with a CLI parameter. The present behaviour could stay as-is for the default (no CLI provided) cases.
Also, if kurtosis would detect more than 1 running engine (in more than 1 namespace), it could fail with a message to specify the desired engine via CLI.
How important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.
What area of the product does this pertain to?
CLI: the Command Line Interface
The text was updated successfully, but these errors were encountered: