Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
cfa10ae9
Commit
cfa10ae9
authored
Dec 06, 2019
by
Alexander Tanayno
Committed by
Achilleas Pipinellis
Dec 06, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add the command for restarting GitLab helm chart
parent
eefa6f35
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
0 deletions
+14
-0
doc/administration/restart_gitlab.md
doc/administration/restart_gitlab.md
+14
-0
No files found.
doc/administration/restart_gitlab.md
View file @
cfa10ae9
...
...
@@ -8,6 +8,7 @@ If you want the TL;DR versions, jump to:
-
[
Omnibus GitLab restart
](
#omnibus-gitlab-restart
)
-
[
Omnibus GitLab reconfigure
](
#omnibus-gitlab-reconfigure
)
-
[
Source installation restart
](
#installations-from-source
)
-
[
Helm chart installation restart
](
#helm-chart-installations
)
## Omnibus installations
...
...
@@ -143,3 +144,16 @@ If you are using other init systems, like systemd, you can check the
[
chef
]:
https://www.chef.io/products/chef-infra/
"Chef official website"
[
src-service
]:
https://gitlab.com/gitlab-org/gitlab/blob/master/lib/support/init.d/gitlab
"GitLab init service file"
[
gl-recipes
]:
https://gitlab.com/gitlab-org/gitlab-recipes/tree/master/init
"GitLab Recipes repository"
## Helm chart installations
There is no single command to restart the entire GitLab application installed via
the
[
cloud native Helm Chart
](
https://docs.gitlab.com/charts/
)
. Usually, it should be
enough to restart a specific component separately (
`gitaly`
,
`unicorn`
,
`workhorse`
,
`gitlab-shell`
, etc.) by deleting all the pods related to it:
```
bash
kubectl delete pods
-l
release
=
<helm release name>,app
=
<component name>
```
The release name can be obtained from the output of the
`helm list`
command.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment