• Helm Commands Cheat Sheet Pdf
• Helm Commands Cheat Sheet

This is a list of useful information regarding Kubernetes that the GitLab SupportTeam sometimes uses while troubleshooting. GitLab is making this public, so that anyonecan make use of the Support team's collected knowledge

WARNING:These commands can alter or break your Kubernetes components so use these at your own risk.

List of Helm CLI commands and it’s purpose: SETUP # initialize helm helm init # update helm MAC brew upgrade kubernetes-helm helm init —upgrade LINUX curl -fsSL -o gethelm.sh chmod 700 g. Microk8s tips and tricks. Pushing to this insecure registry may fail in some versions of Docker unless the daemon is explicitly configured to trust this registry.

If you are on a paid tier and are not sure howto use these commands, it is best to contact Supportand they will assist you with any issues you are having.

Generic Kubernetes commands

• How to authorize to your GCP project (can be especially useful if you have projectsunder different GCP accounts):

• How to access Kubernetes dashboard:

• How to SSH to a Kubernetes node and enter the container as roothttps://github.com/kubernetes/kubernetes/issues/30656:

  • For GCP, you may find the node name and run gcloud compute ssh node-name.
  • List containers using docker ps.
  • Enter container using docker exec --user root -ti container-id bash.

• How to copy a file from local machine to a pod:

• What to do with pods in CrashLoopBackoff status:

  • Check logs via Kubernetes dashboard.

  • Check logs via Kubectl:

• How to tail all Kubernetes cluster events in real time:

• How to get logs of the previously terminated pod instance:

  No logs are kept in the containers/pods themselves. Everything is written to stdout.This is the principle of Kubernetes, read Twelve-factor appfor details.

• How to get cron jobs configured on a cluster

  When one configures cron-based backups,you will be able to see the new schedule here. Some details about the schedules can be foundin Running Automated Tasks with a CronJob

GitLab-specific Kubernetes information

• Minimal configuration that can be used to test a Kubernetes Helm chart.

• Tailing logs of a separate pod. An example for a webservice pod:

• Tail and follow all pods that share a label (in this case, webservice):

• One can stream logs from all containers at once, similar to the Omnibuscommand gitlab-ctl tail:

• Check all events in the gitlab namespace (the namespace name can be different if youspecified a different one when deploying the Helm chart):

• Most of the useful GitLab tools (console, Rake tasks, etc) are found in the task-runnerpod. You may enter it and run commands inside or run them from the outside:

  You can also use gitlab-rake, instead of /usr/local/bin/gitlab-rake.

• Troubleshooting Operations > Kubernetes integration:

  • 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 installedvia Helm Chart, kubernetes.log can be found inside the Sidekiq pod.

• How to get your initial administrator password https://docs.gitlab.com/charts/installation/deployment.html#initial-login:

• How to connect to a GitLab PostgreSQL database:

• How to get information about Helm installation status:

• How to update GitLab installed using Helm Chart:

  After https://gitlab.com/gitlab-org/charts/gitlab/-/issues/780 is fixed, it shouldbe possible to use Updating GitLab using the Helm Chartfor upgrades.

• How to apply changes to GitLab configuration:

  • Modify the gitlab.yaml file.

  • Run the following command to apply changes:

• How to get the manifest for a release. It can be useful because it contains the information aboutall Kubernetes resources and dependent charts:

Installation of minimal GitLab configuration via Minikube on macOS

This section is based on Developing for Kubernetes with Minikubeand Helm. Referto those documents for details.

• Install Kubectl via Homebrew:

• Install Minikube via Homebrew:

• Start Minikube and configure it. If Minikube cannot start, try running minikube delete && minikube startand repeat the steps:

• Install Helm via Homebrew and initialize it:

• Copy the Minikube minimum values YAML fileto your workstation:

• Find the IP address in the output of minikube ip and update the YAML file withthis IP address.

• Install the GitLab Helm Chart:

  If you want to modify some GitLab settings, you can use the above-mentioned configurationas a base and create your own YAML file.

• Monitor the installation progress via helm status gitlab and minikube dashboard.The installation could take up to 20-30 minutes depending on the amount of resourceson your workstation.

• When all the pods show either a Running or Completed status, get the GitLab password asdescribed in Initial login,and log in to GitLab via the UI. It will be accessible via https://gitlab.domainwhere domain is the value provided in the YAML file.

• PDF Link: cheatsheet-openshift-A4.pdf, Category: Cloud
• Blog URL: https://cheatsheet.dennyzhang.com/cheatsheet-openshift-A4
• Related posts: PKS CheatSheet, Kubectl CheatSheet, #denny-cheatsheets

File me Issues or star this repo.

1.1 OpenShift FAQ

1.2 OpenShift Key Components

1.3 New Concepts From OpenShift

1.4 OpenShift Solutions

1.5 OpenShift Glossary

1.6 OpenShift Assumptions

1.7 OpenShift Maintainance

1.8 OpenShift Cfg Files

1.9 OC – Highlights

Helm Commands Cheat Sheet Pdf

1.10 OC – Admin

1.11 OC – Developer

Helm Commands Cheat Sheet

1.12 OpenShift Source Code

1.13 OpenShift Opportunty

1.16 More Resources

License: Code is licensed under MIT License.