Skip to content

Conversation

@harshini-rangaswamy
Copy link
Collaborator

@harshini-rangaswamy harshini-rangaswamy commented Dec 10, 2025

Describe your changes

Documentation updates for the Inkless Cloud internal release, including:

  • Updates to the Kafka service creation flow to reflect Inkless and Classic Kafka service types and deployment modes.
  • A new Inkless overview describing core concepts, key differences from Classic Kafka, and behavior for existing services.
  • Documentation for the AKU-based usage and billing model, covering compute (AKU-hours), storage, and topic ingress and egress.

Autoscaling documentation is not included.

POD-1752

Preview:

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/.

@github-actions github-actions bot added service/kafka tech Relates to technical updates of the docs platform. labels Dec 10, 2025
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Dec 10, 2025

Deploying aiven-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4ec0058
Status: ✅  Deploy successful!
Preview URL: https://7a0923d4.aiven-docs.pages.dev
Branch Preview URL: https://pod-1752-documentation-for-i.aiven-docs.pages.dev

View logs

@harshini-rangaswamy harshini-rangaswamy force-pushed the POD-1752-documentation-for-inkless-saa-s branch from 4ccc992 to deb1a0e Compare December 10, 2025 10:01
@harshini-rangaswamy harshini-rangaswamy self-assigned this Dec 10, 2025
- Classic topics use local disk for recent data and move older segments to object storage
through tiered storage.

Storage and compute scale independently, so you can adjust retention without changing
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's confirm, it will have some affect. e.g. if high throughput topic you will be tiering a lot more data, which takes CPU

- Classic topics keep a short amount of recent data on local disk before offloading older
data to object storage.

Local disk used by brokers is not billed.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Local disk used by brokers is not billed.

Copy link
Contributor

Choose a reason for hiding this comment

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

I need to check, but I think it is included in storage total, rather than not billed

- **Ingress:** Data written to topics
- **Egress:** Data read by consumers, connectors, or mirroring processes

Network usage is measured at the service level across all topics.
Copy link
Contributor

Choose a reason for hiding this comment

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

This will likely be split by topic type

Copy link
Contributor

@Stuzanna Stuzanna left a comment

Choose a reason for hiding this comment

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

@harshini-rangaswamy thanks for the work so far, I have left some comments to do with phrasing on number of AKU , rather than level, and where we will want to add more as the PR develops.

@harshini-rangaswamy
Copy link
Collaborator Author

@harshini-rangaswamy thanks for the work so far, I have left some comments to do with phrasing on number of AKU , rather than level, and where we will want to add more as the PR develops.

Thanks for the review. I have updated the wording to use number of AKUs instead of AKU level. The remaining comments are pending confirmation.

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

Labels

service/kafka tech Relates to technical updates of the docs platform.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants