-
Notifications
You must be signed in to change notification settings - Fork 83
Add a new page on how to restart a pod on Kubernetes #2618
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
Open
NataliaIvakina
wants to merge
1
commit into
neo4j:dev
Choose a base branch
from
NataliaIvakina:dev-kubernetes-ops-update
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+36
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
33 changes: 33 additions & 0 deletions
33
modules/ROOT/pages/kubernetes/operations/change-configuration.adoc
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
:description: The page describes how to restart Neo4j pods in case of modifying ConfigMaps or secrets. | ||
|
||
= Make a configuration change | ||
|
||
When you update ConfigMaps or secrets (for example, updating GDS or Bloom license values), you have to restart your Neo4j pod so that the changes take effect. | ||
|
||
You have two options for restarting: | ||
|
||
* To run the `kubectl delete pod` command as follows: | ||
+ | ||
[source, shell] | ||
---- | ||
kubectl delete pod <pod_name> | ||
---- | ||
+ | ||
You manually delete the Neo4j pod. | ||
Kubernetes will automatically recreate it with the updated configuration. | ||
|
||
* To use the `kubectl rollout restart` command: | ||
+ | ||
[source, shell] | ||
---- | ||
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. | ||
This process is safer and ensures that your application remains available throughout the restart process. | ||
|
||
|
||
If you need to change Neo4j password, see xref:kubernetes/operations/reset-password.adoc[]. | ||
|
||
For information on how to install and manage plugins, refer to the xref:kubernetes/plugins.adoc[]. | ||
|
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would that work regarding the volumes attached to neo4j ( both needing lock ) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.