Feature Request: Improve installation flow for Kubewarden stack

[jordojordo]

Is your feature request related to a problem?

Installing the Kubewarden stack should be a simple process - currently the three helm charts (kubewarden-crds, kubewarden-controller, and kubewarden-defaults) need to be installed separately, along with the cert-manager and the open-telemetry-operator.

Also if the user would like Tracing or Monitoring they are required to install Jaeger and Rancher Monitoring.

Solution you'd like

Emulate the Monitoring App wizard:

• Each chart has it's own tab with questions
• Let user decide which features they would like installed
  • This would include creating the necessary config maps

Todo

• Create guided steps to enable prerequisites before installation #101
• feat: Add questions.yaml to kubewarden-defaults kubewarden/helm-charts#172
• feat: Add custom installation page for kubewarden-controller #204

Related

#83 - The integration with ArtifactHub will tie into the installation process

[viccuad]

Blocked by kubewarden/rfc#7.

[jordojordo]

From a discussion with the Kubewarden and Rancher UI team, the installation of the UI should involve a custom flow within the Overview page of the plugin.

flowchart LR
subgraph Plugin install
id1[Install plugin]-->id2[Kubewarden Overview page]
end

subgraph Kubewarden install
id2-->id3[Install Kubewarden from uber helm-chart]
id3==>id4[Kubewarden-ontroller]
id3==>id5[Default policy server]
id3-.->dp(Kubewarden-defaults)
end

subgraph Optional addons
id3-.->id6((Monitoring))
id6==>id8[Open-telemetry]
id6-->m1(Prometheus, Grafana, ConfigMap)
id3-.->id7((Tracing))
id7==>id8
id7-->t1(JaegerOperator, Jaeger Resource)
end

Loading

Charts Needed for optional installations:

• Monitoring ( open-telemetry, prometheus, grafana )
• Tracing ( open-telemetry, JaegerOperator )

If the user opts out of the optional Monitoring addon and decides to install it separately there should be an option in the Monitoring chart to update the Kubewarden-controller config