Gitea Installation via Helm on Apple M1

Hits: 103

Gitea? is aa community developed and managed simple, lightweight github alternative, written in Go.

Gitea provides a Helm Cart for installation on kubernetes, thats mean, if we would like to customize our install, we can do this.. But when not, we can directly use without any custom configuration/helm config.


helm repo add gitea-charts
helm repo update && helm install gitea gitea-charts/gitea
MBP-von-Koray ~ % helm repo update && helm install gitea gitea-charts/gitea
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "gitea-charts" chart repository
Update Complete. ⎈Happy Helming!⎈
NAME: gitea
LAST DEPLOYED: Sun Aug  1 14:07:36 2021
NAMESPACE: default
STATUS: deployed
1. Get the application URL by running these commands:
  echo "Visit to use your application"
  kubectl --namespace default port-forward svc/gitea-http 3000:3000

And starting port-forwarding for Port 3000.

kubectl --namespace default port-forward svc/gitea-http 3000:3000

and here is.. Enjoy 😊

To customize your install, here is the complete configuration details.

Helm CLI installation on Apple M1

Hits: 3908

Helm? is a package manager for Kubernetes. Helm uses a packaging format, this called “charts”.

Chart? is a collection of files, what be describe Kubernetes resources, like a Server, Database, Caches or simple deploy pod.

Check first first which version as lastest for ARM64 released :

Installation Step

Run following console commands in command line. IMPORTANT! Don’t Forget replacing this LASTEST-RELEASE-HERE tag with latest release/version from For example

  • Download your Helm CLI Binary
curl -O
  • Unpack it
tar -zxvf helm-LASTEST-RELEASE-HERE-linux-amd64.tar.gz
  • And Move it to bin location
sudo mv darwin-arm64/helm /usr/local/bin/helm

and, you should be able to run, check with this command and see the output

koray@MBP-von-Koray ~ % helm help
The Kubernetes package manager

Common actions for Helm:

- helm search:    search for charts
- helm pull:      download a chart to your local directory to view
- helm install:   upload the chart to Kubernetes
- helm list:      list releases of charts

Environment variables:

| Name                               | Description                                                                       |
| $HELM_CACHE_HOME                   | set an alternative location for storing cached files.                             |
| $HELM_CONFIG_HOME                  | set an alternative location for storing Helm configuration.                       |
| $HELM_DATA_HOME                    | set an alternative location for storing Helm data.                                |
| $HELM_DEBUG                        | indicate whether or not Helm is running in Debug mode                             |
| $HELM_DRIVER                       | set the backend storage driver. Values are: configmap, secret, memory, postgres   |

Example Steps with Today’s version

koray@MBP-von-Koray ~ % curl -O
koray@MBP-von-Koray ~ % tar -zxvf helm-v3.6.3-darwin-arm64.tar.gz 
koray@MBP-von-Koray ~ % sudo mv darwin-arm64/helm /usr/local/bin/helm

Minikube on an Apple M1

Hits: 1855

Minikube? is local Kubernetes.

Kubernetes? is open source portable and flexible platform for managing containerized services, we have also declarative configuration and automation for services.

Docker Desktop on Apple M1

First thing, what we needed, it’s a Docker Desktop App for Apple Silicon.

Please check the Official Installation Guide, if installation steps changes has or new steps added..)

Docker Installation on Apple M1:

  • Download Docker Setup
  • Install Rosetta 2 Binaries
    • To install manually from the command line, run the following command
softwareupdate --install-rosetta

Important We Starting the Docker Desktop app after installation! (because i don’t did that!!!)

ok, so now docker desktop up and running…


Minikube also has Official Installation Guide, please check the Official documentation, if the steps has changes or new steps added.

Why? because Docker and Minikube working ever day for integration for Apple Silicon, that means for us, the Installation Requirements or steps can be changes in the future.

Today’s minikube installation Steps, run following command in command line.

  • Download Minikube release
curl -LO
  • Install Minikube
sudo install minikube-darwin-amd64 /usr/local/bin/minikube

After Minikube Installation, we should be able to start minikube. Actually one drive supported. Its’a docker, that means, we must be the driver as argument for minikube start given.

minikube start --driver=docker

with this command, minikube will download kubernetes required docker images, this can take a little longer.

everything looks good and minikube working very well. Let’s starting we the dashboard.. for that run followed single command in command line.

minikube dashboard

and here is..

Gitlab Installation WSL2 + Docker + Kubernetes + Helm 3

Hits: 574

helm create gitlab gitlab/gitlab
kubectl create namespace gitlab


## GitLab Edition
### ref:
### - CE - Community Edition
### - EE - Enterprise Edition - (requires license issued by GitLab Inc)
edition: CE
### GitLab CE image
### ref:
ceImage: gitlab/gitlab-ce:9.1.2-ce.0


## Enable persistence using Persistent Volume Claims
## ref:
## ref:
  ## This volume persists generated configuration files, keys, and certs.
    enabled: true
    size: 1Gi
    ## If defined, <storageClass>
    ## Default: default
    # storageClass:
    accessMode: ReadWriteOnce
  ## This volume is used to store git data and other project files.
  ## ref:
    enabled: true
    size: 10Gi
    ## If defined, <storageClass>
    ## Default: default
    # storageClass:
    accessMode: ReadWriteOnce
    enabled: true
    size: 10Gi
    ## If defined, <storageClass>
    ## Default: default
    # storageClass:

      # storageClass:
      size: 10Gi
  ## Configuration values for the Redis dependency.
  ## ref:
      # storageClass:
      size: 10Gi

externalUrl: 'https://gitlab.local'

omnibusConfigRuby: |
  # This is example config of what you may already have in your omnibusConfigRuby object
  unicorn['worker_processes'] = 2;
  gitlab_rails['trusted_proxies'] = ["","",""];

  registry_external_url 'https://containerregistry.local';

  # These are the settings needed to support proxied SSL
  nginx['listen_port'] = 80
  nginx['listen_https'] = false
  nginx['proxy_set_headers'] = {
    "X-Forwarded-Proto" => "https",
    "X-Forwarded-Ssl" => "on"
  registry_nginx['listen_port'] = 80
  registry_nginx['listen_https'] = false
  registry_nginx['proxy_set_headers'] = {
    "X-Forwarded-Proto" => "https",
    "X-Forwarded-Ssl" => "on"

  enabled: true
  annotations: nginx
   # 'true' Annotation used for letsencrypt support

    - gitlab.local
    - containerregistry.local

    ## gitlab Ingress TLS configuration
    ## Secrets must be created in the namespace, and is not done for you in this chart

#    tls:
#      - secretName: gitlab-tls
#        hosts:
#          - gitlab.local
#          - containerregistry.local
helm install --namespace=gitlab gitlab -f values.yaml gitlab/gitlab

Create Docker Image with Tag from .tar file and push in Private Docker Registery

Hits: 654

Create Docker Image from .tar file

$ docker load --input my-dockerized-app-0.0.1.tar

Create a tag.

Before tag creating, i will learn my source image/newly created docker image ID for the tag creating command..


we can find that via “docker image ls”, but put the grep command, because i want only the same name having images seen, what I as grep argument given.

$ docker image ls | grep my-docker
my-dockerized-app                        0.0.1       c0f32faf4320   1 minute ago      

And now i can create a new tag for local or for private docker registry

Option 1. Tag for Only Local Using

$ docker tag c0f32faf4320 my-dockerized-app:0.0.1

Option 2. Tag for Local and over Local/Open Registry

$ docker tag c0f32faf4320
$ docker push

Example Usage:

in docker-compose.yml

version: '3'
        image: my-dockerized-app:0.0.1

for Kubernetes deployment

apiVersion: apps/v1
kind: Deployment
  name: app-deployment
    app: app-test
  replicas: 1
      app: app-test
        app: app-test
      - name: frontend
        image: my-dockerized-app:0.0.1 // or (dont forget use the imagePullSecrets for privat Registry)