Implement proper scaling rules for all container apps #1293
Comments
4 tasks
arealmaas
added a commit
that referenced
this issue
Oct 16, 2024
<!--- Provide a general summary of your changes in the Title above --> ## Description - Enable automatic scaling based on CPU and memory for graphql and web-api (enduser only) - Setting 70 as the limit, this can be tweaked as we see how the services behave under load - Set a max number of 10 revisions for now. We might need to increase this in yt01 <!--- Describe your changes in detail --> ## Related Issue(s) - #1293 ## Verification - [ ] **Your** code builds clean without any errors or warnings - [ ] Manual testing done (required) - [ ] Relevant automated test added (if you find this hard, leave it and we'll help out) ## Documentation - [ ] Documentation is updated (either in `docs`-directory, Altinnpedia or a separate linked PR in [altinn-studio-docs.](https://github.com/Altinn/altinn-studio-docs), if applicable) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced dynamic scaling configuration for container apps, allowing for minimum and maximum replicas and custom scaling based on CPU and memory utilization. - **Enhancements** - Improved deployment flexibility with a centralized scaling parameter for container apps. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
arealmaas
moved this from New issues
to Done
in ⚠️ Dialogporten / Arbeidsflate - GAMMEL - se https://github.com/orgs/Altinn/projects/146 ⚠️
arealmaas
closed this as completed
by moving to Done
in
⚠️ Dialogporten / Arbeidsflate - GAMMEL - se https://github.com/orgs/Altinn/projects/146 ⚠️
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can be creative here with what kind of event that will trigger a scale-up using https://keda.sh/
For now, implement CPU/MEM as scaling trigger
Beware of web-api that needs to be one replica until events are solved.
The text was updated successfully, but these errors were encountered: