Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Scaling claim on About and Built for Business: how to word HPA and VPA

Open
#226 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
helm, kubernetes, nuxt, php, redis

Research direction

Start with the two claims in content/about.yml (Kubernetes item) and content/built-for-business.yml (Can CWA scale?). Then read pwa-hpa.yaml and hpa.yaml in the components-web-app chart to confirm the replica ranges and that no VPA object exists. The maintainer has not chosen an option yet, so wait for that decision before editing. Done means the chosen option's wording matches the chart in both files.

Written by the indexing model from the issue text.

Description

documentation

The audit rewrite (83697e2) replaced the old claims, and the maintainer wants to decide the final wording.

The old claims were:

  • about.yml (Kubernetes card): "take advantage of HPA and VPA with easy to customise templates using our included Helm chart".
  • built-for-business.yml (FAQ "Can CWA scale?"): "designed to work with server cluster autoscaling (both HPA and VPA) … load-tested … impressive results".

What the template's chart does (components-web-app origin/main):

  • Two HPAs. The Nuxt one (pwa-hpa.yaml) scales from 1 to 6 pods on CPU at a 175% target; CI's production default is 2 to 6. The php one (hpa.yaml) has maxReplicas: 1, because Souin's otter store and Mercure's bolt transport are per pod (#85). The Redis store is built but not used yet.
  • No VPA object. Kubernetes advises against a VPA in Auto mode on pods whose HPA scales on CPU or memory. Both HPAs do, so a VPA in recommendation mode (updateMode: Off) is the safe way to use one.

The options:

  1. Keep the current wording: the front end scales out, and the API is one pod until shared stores exist.
  2. HPAs are included, and you can add a VPA in recommendation mode for sizing. This is the suggested option.
  3. Restore the old wording, if VPA is part of the intended setup.

Current text: content/about.yml (Kubernetes item), content/built-for-business.yml (Can CWA scale?).

Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.