Add a new page on how to restart a pod on Kubernetes #2618
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR includes documentation updates New pages: Updated pages: |
ikwattro
reviewed
Sep 24, 2025
| kubectl rollout restart statefulset/<neo4j-statefulset-name> | ||
| ---- | ||
| + | ||
| A rollout restart means a gradual recreation of a pod — the old pod is not removed entirely until the new pod is running successfully. |
There was a problem hiding this comment.
How would that work regarding the volumes attached to neo4j ( both needing lock ) ?
There was a problem hiding this comment.
Hi! I might be wrong, but as I understand it, the rollout restart command doesn’t affect the volumes attached to the Neo4j pods. It simply restarts the pod. Since the volumes have stable identities (PersistentVolumeClaims), they’ll be re-attached to the newly created pod after the restart.
@riggi-alekaj, please correct me if this is wrong.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.