Document addons about docs HOT 11 CLOSED

Update current add-on configuration for the new possibility to created selectable addons: https://docs.kubermatic.io/advanced/addons/

• describe how to build and configure default add-ons
• describe how to build and configure selectable add-ons

from docs.

I think the build and configuration of addons can be better described by the lifecycle team, @kdomanski WDYT?

from docs.

Agreed.

from docs.

Okay, thanks for the confirmation. I can add a few words connected to the UI/accessible addons setup if needed.

from docs.

/label team/lifecycle

from docs.

/remove-label team/ui

from docs.

As I was working on implementing the UI for the accessible addons here are few things from my side to add to the documentation:

• Accessible addons require additional configuration similar to default addons.
• Accessible addons are the ones that can be changed by the user in the UI. Default addons are the ones that are created with every user cluster. If the addon is both accessible and default at the same time it will be shown in the UI, created along with other default addons and also recreated each time when the user will try to delete it.
• Accessible addons were added in kubermatic/kubermatic#3845.
• Configuration of both accessible and default addons can be found in values.yaml.

cc @toschneck

from docs.

✔️ agree. Please describe the usage from a customer perspective.

from docs.

/assign

Covered it while addon config docs.

from docs.

@maciaszczykm can you please also document, how the addon variables could be used inside of the add-on implementation.Are the handed is environment variables or how can I access the value?
https://docs.loodse.com/kubermatic/master/advanced/addons/#configuration-1

We also should describe a little bit more how the template variables are working https://docs.loodse.com/kubermatic/master/advanced/addons/#template-variables. As end user I would like to see an example how I can extract e.g. from a cluster object the values and use it in a template. Currently it's an guessing what could be used and what not.

from docs.

/label team/lifecycle

from docs.