summaryrefslogtreecommitdiff
path: root/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2019-10-01 03:05:57 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2019-10-01 03:05:57 +0000
commitec60358d52be0dc99f52db94dc95209f1486eac9 (patch)
treeae697a01f32bf46443fcdbdefe9873caf62a18b3 /doc/administration/troubleshooting/kubernetes_cheat_sheet.md
parentb38cf7ccdf8b7ca90bce587a1bf4765631733017 (diff)
downloadgitlab-ce-ec60358d52be0dc99f52db94dc95209f1486eac9.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/troubleshooting/kubernetes_cheat_sheet.md')
-rw-r--r--doc/administration/troubleshooting/kubernetes_cheat_sheet.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/administration/troubleshooting/kubernetes_cheat_sheet.md b/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
index 1247060058b..233cfb9f7cf 100644
--- a/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
+++ b/doc/administration/troubleshooting/kubernetes_cheat_sheet.md
@@ -15,7 +15,7 @@ If you are on a [paid tier](https://about.gitlab.com/pricing/) and are not sure
to use these commands, it is best to [contact Support](https://about.gitlab.com/support/)
and they will assist you with any issues you are having.
-## Generic kubernetes commands
+## Generic Kubernetes commands
- How to authorize to your GCP project (can be especially useful if you have projects
under different GCP accounts):
@@ -33,7 +33,7 @@ and they will assist you with any issues you are having.
kubectl proxy
```
-- How to ssh to a Kubernetes node and enter the container as root
+- How to SSH to a Kubernetes node and enter the container as root
<https://github.com/kubernetes/kubernetes/issues/30656>:
- For GCP, you may find the node name and run `gcloud compute ssh node-name`.
@@ -72,12 +72,12 @@ and they will assist you with any issues you are having.
This is the principle of Kubernetes, read [Twelve-factor app](https://12factor.net/)
for details.
-## GitLab-specific kubernetes information
+## GitLab-specific Kubernetes information
-- Minimal config that can be used to test a Kubernetes helm chart can be found
+- Minimal config that can be used to test a Kubernetes Helm chart can be found
[here](https://gitlab.com/gitlab-org/charts/gitlab/issues/620).
-- Tailing logs of a separate pod. An example for a unicorn pod:
+- Tailing logs of a separate pod. An example for a Unicorn pod:
```bash
kubectl logs gitlab-unicorn-7656fdd6bf-jqzfs -c unicorn
@@ -101,7 +101,7 @@ and they will assist you with any issues you are having.
```
- Check all events in the `gitlab` namespace (the namespace name can be different if you
- specified a different one when deploying the helm chart):
+ specified a different one when deploying the Helm chart):
```bash
kubectl get events -w --namespace=gitlab
@@ -140,8 +140,8 @@ and they will assist you with any issues you are having.
- Check the output of `kubectl get events -w --all-namespaces`.
- Check the logs of pods within `gitlab-managed-apps` namespace.
- - On the side of GitLab check sidekiq log and kubernetes log. When GitLab is installed
- via Helm Chart, `kubernetes.log` can be found inside the sidekiq pod.
+ - On the side of GitLab check Sidekiq log and Kubernetes log. When GitLab is installed
+ via Helm Chart, `kubernetes.log` can be found inside the Sidekiq pod.
- How to get your initial admin password <https://docs.gitlab.com/charts/installation/deployment.html#initial-login>: