Skip to content

ADR specifying the Servala framework requirements#165

Merged
tobru merged 14 commits intomasterfrom
adr-framework-requirements
Oct 28, 2025
Merged

ADR specifying the Servala framework requirements#165
tobru merged 14 commits intomasterfrom
adr-framework-requirements

Conversation

@tobru
Copy link
Member

@tobru tobru commented Sep 30, 2025

To define what the future of our managed applications framework looks like, we clearly specify the requirements in this document.

@bastjan
Copy link
Member

bastjan commented Oct 3, 2025

The platform operator is missing as a persona IMO. I'd want

  • Strong multi-tenancy guarantees
  • Reducing the interfaces between packaged service X and the platform to the minimum required amount to reduce attack surface.
  • Availability - Noisy neighbours should have minimal impacts on other instances or the cluster.
  • Clear separation of concerns

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>

Apply suggestion from @lieneluksika

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>

Apply suggestion from @lieneluksika

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>

Apply suggestion from @lieneluksika

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>

Apply suggestion from @lieneluksika

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>

Apply suggestion from @lieneluksika

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>

Apply suggestion from @lieneluksika

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>

Apply suggestion from @lieneluksika

Co-authored-by: lieneluksika <121873045+lieneluksika@users.noreply.github.com>
@tobru tobru force-pushed the adr-framework-requirements branch from 23cd1ad to 4820608 Compare October 16, 2025 12:24
* configure the service to my requirements
* get meaningful documentation about the service and its parameters
* know about the status of my service instance and its health (metrics, logs)
* stay informed about running costs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* stay informed about running costs
* stay informed about running costs
** know which parameters influence the cost
** know upfront how changes influence the cost

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if we're mixing framework vs. portal stuff here...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed this, and we'll make sure to have this requirements met in the Portal

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There needs to be a single source of truth of cost somewhere. And optimally it would be close to the parametes, otherwise we risk drift.

@tobru tobru marked this pull request as ready for review October 28, 2025 10:28
@tobru tobru merged commit be83258 into master Oct 28, 2025
1 check passed
@tobru tobru deleted the adr-framework-requirements branch October 28, 2025 10:28
@tobru
Copy link
Member Author

tobru commented Oct 28, 2025

We're good to go after discussion in Schedar. We agree that the current state is good to move forward with the next steps. As we learn, we'll adapt this ADR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants