Add robusta to CIVO Cloud marketplace about robusta

[aantn]

@saiyam1814 It seems weird to give instructions in post_install which involve changing the Helm values and redeploying the entire application... It makes the install step a little meaningless.

Is there a fundamental reason why the marketplace doesn't take free-text inputs? (E.g. a desire for simplicity.)

All this said, we can try to work around this if we have to. Not sure what the best solution is, but we'll find something.

[kranurag7]

@aantn I would love to work on this.

[avinashupadhya99]

How will we pass the helm values during installation from Civo marketplace? The marketplace only allows dropdown style inputs from what I have seen so far on the marketplace.

@kranurag7 how do you plan on implementing this?

[aantn]

Yeah, that seems to be an issue.

Generally speaking, I think we want to skip running robusta gen-config and just fill in Helm values from the Civo UI dropdowns.

That won't work for configuring the Slack key and Robusta UI token. We can ask you to run robusta integrations slack to generate a Slack token first, but if there is no way to provide that as input with Civo cloud then that's a problem.

@saiyam1814 any thoughts?

[saiyam1814]

For helm values why not we create a basic best helm values chart - we can get the email and clusterID form the variables.
For the config - we can put those instructions in the Post_install.
We can do the best possible installation, give the config + patch commands in the post_install file

[saiyam1814]

I mean we can provide the best possible values during the installation and then in the post install we can just have the step to install robusta cli and add the slack channel or upgrade the config if required.