Skip to content

Conversation

harshini-rangaswamy
Copy link
Contributor

@harshini-rangaswamy harshini-rangaswamy commented Sep 19, 2025

Describe your changes

Content for Autoscaling BYOC Inkless/Diskess services.
POD-1443

Checklist

  • The first paragraph of the page is on one line.
  • The other lines have a line break at 90 characters.
  • I checked the output.
  • I applied the style guide.
  • My links start with /docs/.

@harshini-rangaswamy harshini-rangaswamy self-assigned this Sep 19, 2025
Copy link

cloudflare-workers-and-pages bot commented Sep 19, 2025

Deploying aiven-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: e160a65
Status: ✅  Deploy successful!
Preview URL: https://06685bfa.aiven-docs.pages.dev
Branch Preview URL: https://pod-1443-phase-1-la-write-in.aiven-docs.pages.dev

View logs

@github-actions github-actions bot added the tech Relates to technical updates of the docs platform. label Sep 19, 2025
@harshini-rangaswamy harshini-rangaswamy added service/kafka and removed tech Relates to technical updates of the docs platform. labels Sep 19, 2025
@github-actions github-actions bot added tech Relates to technical updates of the docs platform. and removed service/kafka labels Sep 22, 2025
Comment on lines 19 to 21
Autoscaling must be enabled when you
[create a Diskless Topics service in BYOC](/docs/products/diskless/howto/create-diskless-topic).
You cannot enable it later on an existing service.

Choose a reason for hiding this comment

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

Technically this is incorrect, I am ok with the text here though.
For clarity, autoscaling will be available based on the deployment plans.
There is a set of autoscaling plans and current plan of the service is checked against these. If plan is found in the set, autoscaling is available.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

For clarity, autoscaling will be available based on the deployment plans.

Thanks! Could you clarify what the deployment plans are, and which ones support autoscaling?

- **Scale down**: When CPU usage is consistently low.
- **Plan switching**: The service scales by switching to the next larger or smaller
autoscaling plan.
- **Scaling in groups**: Nodes are added or removed in fixed groups (for example,

Choose a reason for hiding this comment

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

This is subject to change to vertical scaling. The nodes will get replaced with larger machine types and whole cluster will be rolled.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should we mention this as part of how scaling currently works, or note it as a possible future change?

@harshini-rangaswamy harshini-rangaswamy added service/kafka and removed tech Relates to technical updates of the docs platform. labels Sep 23, 2025
@github-actions github-actions bot added tech Relates to technical updates of the docs platform. and removed service/kafka labels Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech Relates to technical updates of the docs platform.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants