[{"_1":2,"_135":-5,"_136":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_129":130},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_23":24,"_25":26,"_55":56,"_57":-7,"_58":-7,"_59":-7,"_60":-7,"_61":-5,"_62":-5,"_63":11,"_64":11,"_48":65,"_119":17,"_87":88,"_120":86,"_121":47,"_31":32,"_122":11,"_123":17,"_124":125,"_126":-5,"_127":11,"_128":11},"scanningType","none","tagData",{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},"content_type","image","creator",35095401,"digest","sha256:7d11fc6f9e2fa65eb4b6f785d7d9d67566a192bc32a8c1bff2d2b070ec426cb0","full_size",7947,"id",949668229,"images",[],"last_updated","2025-08-07T06:12:06.755219Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.index.v1+json","name","sha256-8b33b2d2ba954769c399cea17eac516bbf72d16cc6c104a2418cc58baddf68aa","repository",19064293,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_66":67,"_72":73,"_75":76,"_77":78,"_79":11,"_39":80,"_81":82,"_83":84,"_46":86,"_87":88,"_89":90,"_91":-5,"_92":93,"_94":93,"_95":96,"_97":-5,"_98":99,"_100":101,"_102":11,"_103":88,"_104":105,"_110":11,"_111":112,"_116":88,"_117":118},"categories",[68],{"_46":69,"_70":71},"Developer tools","slug","developer-tools","content_types",[28,74],"helm","date_registered","2023-01-24T10:49:58.084915Z","description","Bitnami Helm chart for Gitea","is_private","2025-08-13T21:56:27.83827Z","last_modified","2026-03-16T14:23:41.483495Z","media_types",[85,45],"application/vnd.cncf.helm.config.v1+json","gitea","namespace","bitnamicharts","pull_count",1041809,"repository_type","star_count",1,"status","status_description","active","source","collaborator_count",0,"full_description","\n\n# Bitnami Secure Images Helm chart for Gitea\n\nGitea is a lightweight code hosting solution. Written in Go, features low resource consumption, easy upgrades and multiple databases.\n\n[Overview of Gitea](https://gitea.io/)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/gitea\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps a [Gitea](https://github.com/bitnami/containers/tree/main/bitnami/gitea) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\nIt also packages the [Bitnami PostgreSQL chart](https://github.com/bitnami/charts/tree/main/bitnami/postgresql) which is required for bootstrapping a PostgreSQL deployment as a database for the Gitea application.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n- PV provisioner support in the underlying infrastructure\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/gitea\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThe command deploys Gitea on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### Resource requests and limits\n\nBitnami charts allow setting resource requests and limits for all containers inside the chart deployment. These are inside the `resources` value (check parameter table). Setting requests is essential for production workloads and these should be adapted to your specific use case.\n\nTo make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcesPreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).\n\n### [Rolling VS Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Image\n\nThe `image` parameter allows specifying which image will be pulled for the chart.\n\n#### Private registry\n\nIf you configure the `image` value to one in a private registry, you will need to [specify an image pull secret](https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod).\n\n1. Manually create image pull secret(s) in the namespace. See [this YAML example reference](https://kubernetes.io/docs/concepts/containers/images/#creating-a-secret-with-a-docker-config). Consult your image registry's documentation about getting the appropriate secret.\n2. Note that the `imagePullSecrets` configuration value cannot currently be passed to helm using the `--set` parameter, so you must supply these using a `values.yaml` file, such as:\n\n ```yaml\n imagePullSecrets:\n - name: SECRET_NAME\n ```\n\n3. Install the chart\n\n### Update credentials\n\nBitnami charts configure credentials at first boot. Any further change in the secrets or credentials require manual intervention. Follow these instructions:\n\n- Update the user password following [the upstream documentation](https://docs.gitea.com/administration/command-line#admin)\n- Update the password secret with the new values (replace the SECRET_NAME, PASSWORD and SMTP_PASSWORD placeholders)\n\n```shell\nkubectl create secret generic SECRET_NAME --from-literal=admin-password=PASSWORD --from-literal=smtp-password=SMTP_PASSWORD --dry-run -o yaml | kubectl apply -f -\n```\n\n### Gateway API\n\nThis chart provides support for exposing Gitea using the [Gateway API](https://gateway-api.sigs.k8s.io/) and its `HTTPRoute` resource. If you have a Gateway controller installed on your cluster, such as APISIX, Contour, Envoy Gateway, NGINX Gateway Fabric or Kong Ingress Controller you can utilize the Gateway controller to serve your application. To enable Gateway API integration, set `httpRoute.enabled` to `true`.\nThe Gateway to be used can be customized by setting the `httpRoute.parentRefs` parameter. By default, it will reference a Gateway named `gateway` in the same namespace as the release.\n\nYou can specify the list of hostnames to be mapped to the deployment using the `httpRoute.hostnames` parameter. Additionally, you can customize the rules used to route the traffic to the service by modifying the `httpRoute.matches` and `httpRoute.filters` parameters or adding new rules using the `httpRoute.extraRules` parameter.\n\n### Ingress\n\nThis chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as NGINX Ingress Controller or Contour you can utilize the ingress controller to serve your application. To enable Ingress integration, set `ingress.enabled` to `true`.\n\nThe most common scenario is to have one host name mapped to the deployment. In this case, the `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host.\n\nHowever, it is also possible to have more than one host. To facilitate this, the `ingress.extraHosts` parameter (if available) can be set with the host names specified as an array. The `ingress.extraTLS` parameter (if available) can also be used to add the TLS configuration for extra hosts.\n\n> NOTE: For each host specified in the `ingress.extraHosts` parameter, it is necessary to set a name, path, and any annotations that the Ingress controller should know about. Not all annotations are supported by all Ingress controllers, but [this annotation reference document](https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md) lists the annotations supported by many popular Ingress controllers.\n\nAdding the TLS parameter (where available) will cause the chart to generate HTTPS URLs, and the application will be available on port 443. The actual TLS secrets do not have to be generated by this chart. However, if TLS is enabled, the Ingress record will not work until the TLS secret exists.\n\n[Learn more about Ingress controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).\n\n### Setting Pod's affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n## Persistence\n\nThe [Bitnami Gitea](https://github.com/bitnami/containers/tree/main/bitnami/gitea) image stores the Gitea data and configurations at the `/bitnami/gitea` path of the container.\n\nPersistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube.\nSee the [Parameters](#parameters) section to configure the PVC or to disable persistence.\n\n### Existing PersistentVolumeClaim\n\n1. Create the PersistentVolume\n2. Create the PersistentVolumeClaim\n3. Install the chart\n\n```console\nhelm install my-release --set persistence.existingClaim=PVC_NAME oci://REGISTRY_NAME/REPOSITORY_NAME/gitea\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\n### Host path\n\n#### System compatibility\n\n- The local filesystem accessibility to a container in a pod with `hostPath` has been tested on OSX/MacOS with xhyve, and Linux with VirtualBox.\n- Windows has not been tested with the supported VM drivers. Minikube does however officially support [Mounting Host Folders](https://minikube.sigs.k8s.io/docs/handbook/mount/) per pod. Or you may manually sync your container whenever host files are changed with tools like [docker-sync](https://github.com/EugenMayer/docker-sync) or [docker-bg-sync](https://github.com/cweagans/docker-bg-sync).\n\n#### Mounting steps\n\n1. The specified `hostPath` directory must already exist (create one if it does not).\n2. Install the chart\n\n ```console\n helm install my-release --set persistence.hostPath=/PATH/TO/HOST/MOUNT oci://REGISTRY_NAME/REPOSITORY_NAME/gitea\n ```\n\n > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\n This will mount the `gitea-data` volume into the `hostPath` directory. The site data will be persisted if the mount path contains valid data, else the site data will be initialized at first launch.\n3. Because the container cannot control the host machine's directory permissions, you must set the Gitea file directory permissions yourself\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| ------------------- | --------------------------------------------------------------------------------------------------------- | ------ |\n| `kubeVersion` | Force target Kubernetes version (using Helm capabilities if not set) | `\"\"` |\n| `nameOverride` | String to partially override gitea.fullname template (will maintain the release name) | `\"\"` |\n| `fullnameOverride` | String to fully override gitea.fullname template | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\n| `commonAnnotations` | Common annotations to add to all Gitea resources (sub-charts are not considered). Evaluated as a template | `{}` |\n| `commonLabels` | Common labels to add to all Gitea resources (sub-charts are not considered). Evaluated as a template | `{}` |\n| `extraDeploy` | Array of extra objects to deploy with the release (evaluated as a template). | `[]` |\n| `runtimeClassName` | Name of the runtime class to be used by pod(s) | `\"\"` |\n| `usePasswordFiles` | Mount credentials as files instead of using environment variables | `true` |\n\n### Gitea parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- |\n| `image.registry` | Gitea image registry | `REGISTRY_NAME` |\n| `image.repository` | Gitea Image name | `REPOSITORY_NAME/gitea` |\n| `image.digest` | Gitea image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `\"\"` |\n| `image.pullPolicy` | Gitea image pull policy | `IfNotPresent` |\n| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |\n| `image.debug` | Specify if debug logs should be enabled | `false` |\n| `adminUsername` | User of the application | `bn_user` |\n| `adminPassword` | Application password | `\"\"` |\n| `adminEmail` | Admin email | `user@example.com` |\n| `appName` | Gitea application name | `example` |\n| `runMode` | Gitea application host | `prod` |\n| `exposeSSH` | Make the SSH server accessible | `true` |\n| `rootURL` | UI Root URL (for link generation) | `\"\"` |\n| `command` | Override default container command (useful when using custom images) | `[]` |\n| `args` | Override default container args (useful when using custom images) | `[]` |\n| `updateStrategy.type` | Update strategy - only really applicable for deployments with RWO PVs attached | `RollingUpdate` |\n| `priorityClassName` | Gitea pods' priorityClassName | `\"\"` |\n| `schedulerName` | Name of the k8s scheduler (other than default) | `\"\"` |\n| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |\n| `automountServiceAccountToken` | Mount Service Account token in pod | `false` |\n| `hostAliases` | Add deployment host aliases | `[]` |\n| `extraEnvVars` | Extra environment variables | `[]` |\n| `extraEnvVarsCM` | ConfigMap containing extra env vars | `\"\"` \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-gitea-index.html_","has_starred","hub_user","immutable_tags_settings",{"_106":11,"_107":108},"enabled","rules",[109],".*","is_automated","permissions",{"_113":17,"_114":11,"_115":11},"read","write","admin","user","storage_size",17905562,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_23":24,"_59":-7,"_57":-7,"_58":-7,"_25":131,"_31":32,"_133":-7,"_134":11},{"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":132,"_39":40,"_41":30,"_42":43,"_44":45,"_46":47,"_48":49,"_50":-5,"_51":40,"_52":53,"_54":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/gitea:sha256-8b33b2d2ba954769c399cea17eac516bbf72d16cc6c104a2418cc58baddf68aa