diff --git a/.gitea/workflows/changelog.yml b/.gitea/workflows/changelog.yml index 2142eee..08f6283 100644 --- a/.gitea/workflows/changelog.yml +++ b/.gitea/workflows/changelog.yml @@ -20,13 +20,13 @@ jobs: run: | git sv rn -o changelog.md export RELEASE_NOTES=$(cat changelog.md) - export ISSUE_NUMBER=$(curl -s "https://gitea.com/api/v1/repos/gitea/helm-chart/issues?state=open&q=Changelog%20for%20upcoming%20version" | jq '.[].number') + export ISSUE_NUMBER=$(curl -s "https://gitea.com/api/v1/repos/gitea/helm-gitea/issues?state=open&q=Changelog%20for%20upcoming%20version" | jq '.[].number') echo $RELEASE_NOTES JSON_DATA=$(echo "" | jq -Rs --arg title 'Changelog for upcoming version' --arg body "$(cat changelog.md)" '{title: $title, body: $body}') if [ -z "$ISSUE_NUMBER" ]; then - curl -s -X POST "https://gitea.com/api/v1/repos/gitea/helm-chart/issues" -H "Authorization: token ${{ secrets.ISSUE_RW_TOKEN }}" -H "Content-Type: application/json" -d "$JSON_DATA" + curl -s -X POST "https://gitea.com/api/v1/repos/gitea/helm-gitea/issues" -H "Authorization: token ${{ secrets.ISSUE_RW_TOKEN }}" -H "Content-Type: application/json" -d "$JSON_DATA" else - curl -s -X PATCH "https://gitea.com/api/v1/repos/gitea/helm-chart/issues/$ISSUE_NUMBER" -H "Authorization: token ${{ secrets.ISSUE_RW_TOKEN }}" -H "Content-Type: application/json" -d "$JSON_DATA" + curl -s -X PATCH "https://gitea.com/api/v1/repos/gitea/helm-gitea/issues/$ISSUE_NUMBER" -H "Authorization: token ${{ secrets.ISSUE_RW_TOKEN }}" -H "Content-Type: application/json" -d "$JSON_DATA" fi diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 05632bb..e9ebc72 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,7 +38,7 @@ be used: 1. Install `minikube` and `helm`. 1. Start a `minikube` cluster via `minikube start`. -1. From the `gitea/helm-chart` directory execute the following command. +1. From the `gitea/helm-gitea` directory execute the following command. This will install the dependencies listed in `Chart.yml` and deploy the current state of the helm chart found locally. If you want to test a branch, make sure to switch to the respective branch first. `helm install --dependency-update gitea . -f values.yaml`. diff --git a/Chart.yaml b/Chart.yaml index e8f14fe..aa0cd2d 100644 --- a/Chart.yaml +++ b/Chart.yaml @@ -15,9 +15,9 @@ keywords: - gitea - gogs sources: - - https://gitea.com/gitea/helm-chart + - https://gitea.com/gitea/helm-gitea - https://github.com/go-gitea/gitea - - https://hub.docker.com/r/gitea/gitea/ + - https://docker.gitea.com/gitea maintainers: - name: Charlie Drage email: charlie@charliedrage.com diff --git a/README.md b/README.md index 84f3de9..f4c9e19 100644 --- a/README.md +++ b/README.md @@ -65,14 +65,14 @@ It is published under the MIT license. ## Introduction -This helm chart has taken some inspiration from [jfelten's helm chart](https://github.com/jfelten/gitea-helm-chart). +This helm chart has taken some inspiration from [jfelten's helm chart](https://github.com/jfelten/gitea-helm-gitea). Yet it takes a completely different approach in providing a database and cache with dependencies. Additionally, this chart allows to provide LDAP and admin user configuration with values. ## Update and versioning policy The Gitea helm chart versioning does not follow Gitea's versioning. -The latest chart version can be looked up in [https://dl.gitea.com/charts](https://dl.gitea.com/charts) or in the [repository releases](https://gitea.com/gitea/helm-chart/releases). +The latest chart version can be looked up in [https://dl.gitea.com/charts](https://dl.gitea.com/charts) or in the [repository releases](https://gitea.com/gitea/helm-gitea/releases). The chart aims to follow Gitea's releases closely. There might be times when the chart is behind the latest Gitea release. @@ -534,7 +534,7 @@ and the repository exists. ``` To solve this problem add the capability `SYS_CHROOT` to the `securityContext`. -More about this issue [here](https://gitea.com/gitea/helm-chart/issues/161). +More about this issue [here](https://gitea.com/gitea/helm-gitea/issues/161). ### Cache @@ -548,7 +548,7 @@ redis-cluster: enabled: true ``` -⚠️ The redis charts [do not work well with special characters in the password](https://gitea.com/gitea/helm-chart/issues/690). +⚠️ The redis charts [do not work well with special characters in the password](https://gitea.com/gitea/helm-gitea/issues/690). Consider omitting such or open an issue in the Bitnami repo and let us know once this got fixed. ### Persistence @@ -739,7 +739,7 @@ gitea: When using the rootless image the gpg key folder is not persistent by default. If you consider using signed commits for internal Gitea activities (e.g. initial commit), you'd need to provide a signing key. -Prior to [PR186](https://gitea.com/gitea/helm-chart/pulls/186), imported keys had to be re-imported once the container got replaced by another. +Prior to [PR186](https://gitea.com/gitea/helm-gitea/pulls/186), imported keys had to be re-imported once the container got replaced by another. The mentioned PR introduced a new configuration object `signing` allowing you to configure prerequisites for commit signing. By default this section is disabled to maintain backwards compatibility. @@ -1329,7 +1329,7 @@ The first item here (``) will be different compared to th The above changes are motivated by the idea to tidy dependencies but also have HA-ready ones at the same time. The previous `memcache` default was not HA-ready, hence we decided to switch to `redis-cluster` by default. -If you are coming from an existing deployment and [#356](https://gitea.com/gitea/helm-chart/issues/356) is still open, you need to set the config sections for `cache`, `session` and `queue` explicitly: +If you are coming from an existing deployment and [#356](https://gitea.com/gitea/helm-gitea/issues/356) is still open, you need to set the config sections for `cache`, `session` and `queue` explicitly: ```yaml gitea: @@ -1354,7 +1354,7 @@ gitea: If you are facing errors like `WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED` due to this automatic transition: -Have a look at [this discussion](https://gitea.com/gitea/helm-chart/issues/487#issue-220660) and either set `image.rootless: false` or manually update your `~/.ssh/known_hosts` file(s). +Have a look at [this discussion](https://gitea.com/gitea/helm-gitea/issues/487#issue-220660) and either set `image.rootless: false` or manually update your `~/.ssh/known_hosts` file(s). @@ -1410,7 +1410,7 @@ With respect to `values.yaml`, parameters `username`, `database` and `password` Please adjust your `values.yaml` accordingly. **Attention**: The Postgres upgrade is not automatically handled by the chart and must be done by yourself. -See [this comment](https://gitea.com/gitea/helm-chart/issues/452#issuecomment-740885) for an extensive walkthrough. +See [this comment](https://gitea.com/gitea/helm-gitea/issues/452#issuecomment-740885) for an extensive walkthrough. We again highly encourage users to use an external (managed) database for production instances. diff --git a/package-lock.json b/package-lock.json index 1988bc2..838da8b 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,10 +1,10 @@ { - "name": "gitea-helm-chart", + "name": "gitea-helm-gitea", "lockfileVersion": 3, "requires": true, "packages": { "": { - "name": "gitea-helm-chart", + "name": "gitea-helm-gitea", "license": "MIT", "devDependencies": { "@bitnami/readme-generator-for-helm": "^2.5.0", @@ -1660,4 +1660,4 @@ } } } -} +} \ No newline at end of file diff --git a/package.json b/package.json index e9ef85b..358e28f 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { - "name": "gitea-helm-chart", - "homepage": "https://gitea.com/gitea/helm-chart.git", + "name": "gitea-helm-gitea", + "homepage": "https://gitea.com/gitea/helm-gitea.git", "license": "MIT", "private": true, "engineStrict": true, @@ -16,4 +16,4 @@ "@bitnami/readme-generator-for-helm": "^2.5.0", "markdownlint-cli": "^0.44.0" } -} +} \ No newline at end of file diff --git a/templates/gitea/init.yaml b/templates/gitea/init.yaml index 8470a55..5218b86 100644 --- a/templates/gitea/init.yaml +++ b/templates/gitea/init.yaml @@ -94,7 +94,7 @@ stringData: echo "ERROR: 'configure_admin_user' was not able to determine the current list of admin users." echo " Please review the output of 'gitea admin user list --admin' shown below." - echo " If you think it is an issue with the Helm Chart provisioning, file an issue at https://gitea.com/gitea/helm-chart/issues." + echo " If you think it is an issue with the Helm Chart provisioning, file an issue at https://gitea.com/gitea/helm-gitea/issues." echo "DEBUG: Output of 'gitea admin user list --admin'" echo "--" echo "${full_admin_list}" @@ -117,7 +117,7 @@ stringData: else if [[ "${GITEA_ADMIN_PASSWORD_MODE}" = keepUpdated ]]; then echo "Admin account '${GITEA_ADMIN_USERNAME}' already exist. Running update to sync password..." - # See https://gitea.com/gitea/helm-chart/issues/673 + # See https://gitea.com/gitea/helm-gitea/issues/673 # --must-change-password argument was added to change-password, defaulting to true, counter to the previous behavior # which acted as if it were provided with =false. If the argument is present in this version of gitea, then we # should add it to prevent requiring frequent admin password resets. @@ -154,7 +154,7 @@ stringData: echo "ERROR: 'configure_ldap' was not able to determine the current list of authentication sources." echo " Please review the output of 'gitea admin auth list --vertical-bars' shown below." - echo " If you think it is an issue with the Helm Chart provisioning, file an issue at https://gitea.com/gitea/helm-chart/issues." + echo " If you think it is an issue with the Helm Chart provisioning, file an issue at https://gitea.com/gitea/helm-gitea/issues." echo "DEBUG: Output of 'gitea admin auth list --vertical-bars'" echo "--" echo "${full_auth_list}" @@ -198,7 +198,7 @@ stringData: echo "ERROR: 'configure_oauth' was not able to determine the current list of authentication sources." echo " Please review the output of 'gitea admin auth list --vertical-bars' shown below." - echo " If you think it is an issue with the Helm Chart provisioning, file an issue at https://gitea.com/gitea/helm-chart/issues." + echo " If you think it is an issue with the Helm Chart provisioning, file an issue at https://gitea.com/gitea/helm-gitea/issues." echo "DEBUG: Output of 'gitea admin auth list --vertical-bars'" echo "--" echo "${full_auth_list}" diff --git a/unittests/helm/deployment/image-configuration.yaml b/unittests/helm/deployment/image-configuration.yaml index 8b419aa..4a09a26 100644 --- a/unittests/helm/deployment/image-configuration.yaml +++ b/unittests/helm/deployment/image-configuration.yaml @@ -94,7 +94,7 @@ tests: - it: correctly renders floating tag references template: templates/gitea/deployment.yaml set: - image.tag: 1.21 # use non-quoted value on purpose. See: https://gitea.com/gitea/helm-chart/issues/631 + image.tag: 1.21 # use non-quoted value on purpose. See: https://gitea.com/gitea/helm-gitea/issues/631 asserts: - equal: path: spec.template.spec.initContainers[0].image diff --git a/values.yaml b/values.yaml index a30c8bb..f5022d9 100644 --- a/values.yaml +++ b/values.yaml @@ -76,7 +76,7 @@ containerSecurityContext: {} # # run pods on nodes that use the container runtime cri-o. Otherwise, you will # # get an error message from the SSH server that it is not possible to read from # # the repository. -# # https://gitea.com/gitea/helm-chart/issues/161 +# # https://gitea.com/gitea/helm-gitea/issues/161 # add: # - SYS_CHROOT # privileged: false @@ -610,7 +610,7 @@ gitea: ## @section redis-cluster ## @param redis-cluster.enabled Enable redis cluster -# ⚠️ The redis charts do not work well with special characters in the password (). +# ⚠️ The redis charts do not work well with special characters in the password (). # Consider omitting such or open an issue in the Bitnami repo and let us know once this got fixed. ## @param redis-cluster.usePassword Whether to use password authentication ## @param redis-cluster.cluster.nodes Number of redis cluster master nodes @@ -628,7 +628,7 @@ redis-cluster: ## @section redis ## @param redis.enabled Enable redis standalone or replicated ## @param redis.architecture Whether to use standalone or replication -# ⚠️ The redis charts do not work well with special characters in the password (). +# ⚠️ The redis charts do not work well with special characters in the password (). # Consider omitting such or open an issue in the Bitnami repo and let us know once this got fixed. ## @param redis.global.redis.password Required password ## @param redis.master.count Number of Redis master instances to deploy