Unsolved questions

• [ ] How will the APIs and UI for the dashboard be accessed via the core?
  • [ ] Will the APIs be scoped via a /dashboard/ path?
  • [ ] Which port? Same as 3567 or whichever they choose?
• [ ] For certain features like healthcheck, each instance must be cluster aware. How do we achieve this?
• [ ] Some features and UI will be dictated by the recipe. How can we inject features & UI into the dashboard from the recipe?

Authentication (OSS + paid tier)

• Open source
  • Email & password
• Paid tier
  • SAML / LDAP

Authorization (paid tier)

• Role based

Healthcheck (paid tier)

• Cluster and instance health checking
• Integrations with pagerduty and other similar products

Configuration (OSS)

• Set config.yaml file values. With this, most docker env values will be redundant, except for database access values. All others can be stored in the database itself.

User management