Allow for disabling of Components about yatai HOT 4 CLOSED

Hi @knechtionscoding - thank you for the feedback! The reason for installing these components by Yatai instead of the Helm chat, is for Yatai to support multiple clusters. This way, users can bringing in additional k8s cluster to be managed by one Yatai instance. It's indeed a problem that it becomes less customizable this way, I think a better approach is to have a separate Yatai-cluster-components helm chat, which is required to be installed before adding a cluster to Yatai.

Note that currently only the deployment component is installed by default. The logging and monitoring component are disabled by default, and can be installed from the Cluster UI page by the user. Does this work for your current setting?

from yatai.

No, because the namespaces are still created by the yatai operator, even if the parts deployed are disabled.

Means that if you have requirements around labels/settings the NS must have it's not clear who owns it.

from yatai.

I'd definitely prefer the separate chart approach because it would afford a lot more flexibility and control.

from yatai.

@knechtionscoding

Hey, as discussed on slack, We made PRs (bentoml/yatai-chart#40 and #237) to address this issue.

Feel free to have more reopen it.

from yatai.