Altinity / Altinity/clickhouse-operator

Does AWS PVC storage support online expansion without restarting the container?

Open
#946 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
Go
Stars
2.6k
Forks
574
Avg merge
8d 6h
Merged PRs (30d)
6

Description

AWS can re-scale EBS volumes, without shutting down the container upfront.
So can we provide a way to control allowing for example Storage resources to modify the PVC directly without rebuilding the container?

For reference, vitess-operator handles it like this:

  updateStrategy:
    external:
      allowResourceChanges:
      - storage
    type: External

link: https://github.com/planetscale/vitess-operator/blob/main/docs/api.md#planetscale.com/v2.ExternalVitessClusterUpdateStrategyOptions

Thank you so much! Please let me know if you have any suggestions or concerns.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the linked Vitess Operator API example for an external update strategy and compare its storage behavior with this operator's current PVC handling. Trace the existing storage update flow, then define how an allowed storage change should update the PVC without rebuilding or restarting the container.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, kubernetes
Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.