-
Notifications
You must be signed in to change notification settings - Fork 304
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
[nats helm 1.x] nats-server pid location changes based on configuration #759
Comments
This is by design. When the reloaded is enabled, the PID file needs to be accessible by both the When the When the 0.x may have always been making this volume. But it is not necessary to make when the reloader is not enabled so 1.x changes to only make the volume if it is needed. |
@caleblloyd Sorry to piggyback on this issue. I have reloader disabled, but am running all containers as non-root. As a temporary fix, I added to my config: container:
patch:
- op: add
path: /volumeMounts/-
value:
mountPath: /var/run
name: var-run
podTemplate:
patch:
- op: add
path: /spec/volumes/-
value:
emptyDir: {}
name: var-run |
Ah, I had not considered the unprivileged use case. Seems that it is best to always make the |
Using Helm chart
nats-1.0.0-beta6
With:
The
nats-server
pid file is found at:/var/run/nats.pid
With:
The
nats-server
pid file is found at a different location:/var/run/nats/nats.pid
The text was updated successfully, but these errors were encountered: