Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add PV support to the executor statefulset #7

Merged
merged 1 commit into from
Jun 17, 2024
Merged

Add PV support to the executor statefulset #7

merged 1 commit into from
Jun 17, 2024

Conversation

noggi
Copy link
Contributor

@noggi noggi commented Jun 17, 2024

As titled. PV is disabled by defAult.

@darnaut @eboneil @jjoyce0510

existingClaim: ""
mountPath: /tmp/datahub
size: 100Gi
# storageClass: "-"
Copy link
Contributor

Choose a reason for hiding this comment

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

what is an example value here?

do you thik their engineers will understand how to correctly configure to store on say S3?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

if that parameter is omitted, this will use default storage class configured in their cluster. I'd not go with S3 volumes, because that path is used by ingestions to store venv and logs. We actually use similar config in ECS (cloudformation).

Alternatively, they can mount it under a different path (e.g. /memory-profiles), and then use S3 volumes, but I'm not sure their kube cluster supports it. Usually EBS gp2/gp3 is the only supported volume type in AWS deployments.

@noggi noggi merged commit 7c1f2a6 into main Jun 17, 2024
@noggi noggi deleted the ak--pv-support branch June 17, 2024 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants