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

helm: stan, volumeClaim configuration #59

Merged
merged 1 commit into from
May 17, 2020
Merged

Conversation

mcuadros
Copy link
Contributor

@mcuadros mcuadros commented May 17, 2020

This allows to use the volumeClaimTemplate for the logs and the store. Otherwise, the cluster cannot recover their state, see nats-io/nats-streaming-server#547

https://github.com/nats-io/nats-streaming-server/pull/548/files

Also, the support for choosing the storageClass has been introducing, and the default size has been changed to something more performance since usually small disk have low I/O in cloud platforms.

Copy link
Member

@wallyqs wallyqs left a comment

Choose a reason for hiding this comment

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

LGTM, thank you Máximo

@wallyqs wallyqs merged commit dad8b83 into nats-io:master May 17, 2020
@wallyqs
Copy link
Member

wallyqs commented May 20, 2020

Thanks @orefalo I tried locally didn't get an error but maybe have introduced an issue during an upgrade, I will take another look

helm install stan ./helm/charts/stan 

@samstride
Copy link

@wallyqs , Hi, just checking timelines for pushing this chart into helm stable repo? It looks like it will fix #58 for me. Cheers.

@wallyqs
Copy link
Member

wallyqs commented May 25, 2020

Hey @samstride sorry for the wait, I'm aiming at releasing a new version the charts in a couple of days.

@orefalo
Copy link

orefalo commented May 25, 2020

Thanks, will try again in a few days (with the new chart) and provide the complete log.

volume:
enabled: true
mount: /data/stan
storageSize: 100Gi
Copy link
Member

Choose a reason for hiding this comment

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

1Gi -> 100Gi. Sounds good... Were there any issues?

Copy link
Member

Choose a reason for hiding this comment

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

I think I will lower this down back to 1Gi by default otherwise will get an error when upgrading since cannot be changed on the fly.

Copy link
Member

@ColinSullivan1 ColinSullivan1 left a comment

Choose a reason for hiding this comment

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

LGTM.

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.

5 participants