Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: midnightconman Assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @midnightconman. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @foxish |
There's another PR for Gitea: #3408 You may want to join forces. |
/assign |
Would your |
The following table lists some of the configurable parameters of the Gitea | ||
chart and their default values. | ||
|
||
| Parameter | Description | Default | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No sure what it's worth, but usually other Charts list every possible configuration settings of values.yaml. I'm not sure if that's really a benefit, because your values.yaml seems to have enough comments. Anyway, that's just my 2 cents
|
||
## Enable this to use captcha validation for registration. | ||
## | ||
serverDomain: gitea.example.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment and the key does not seems to go toogether
## Persistent Volume Storage configuration. | ||
## ref: https://kubernetes.io/docs/user-guide/persistent-volumes | ||
## | ||
persistence: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you allow one to specify a existing PVC ? For exmaple jenkins does this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, that works... read line 249.
## | ||
databaseType: postgres | ||
|
||
## Database host. Unused unless `postgresql.install` is false. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Double negatives are hard to read and understand, could you use "Used only when postgresql.install
is true." ? thanks :)
well darn it - I just created my own similar gitea chart since this PR was not there when I started. Feel free to borrow anything from my chart if helpful or let me know how I can help: |
used this chart to setup Gitea, having some trouble reading configI don't think it's picking up the config at all..
copied the config, but got an error
postgresqladding
But initContainers should be fixed to copy the config to the right place, if I understand the issue correctly.
indexerIssuePathis defined as
changing it to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A newer version of Gitea is out.
|
||
image: | ||
repository: gitea/gitea | ||
tag: 1.4.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gitea 1.5.1 is out.
@@ -0,0 +1,12 @@ | |||
apiVersion: v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this only be created if .Values.postgresql.create=true?
- name: data | ||
mountPath: /data | ||
- name: config-rw | ||
mountPath: /etc/gitea/conf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect you mean to mount this to /etc/templates/
so that it gets consumed by https://github.com/go-gitea/gitea/blob/6e03390aa8fa096206457962db1955d642860b57/docker/etc/s6/gitea/setup#L39 on initial start up
On top of the 2 comments I have made, It should be noted that the config file that is used is in One solution would be to have a pre-upgrade hook that deletes I suspect, the config could simply be mounted to Another thing I noticed while investigating this chart is that there is a difference between the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all tested, and perfect
Hello :) What is the state of this project branch ? |
What this PR does / why we need it:
Adds a helm chart for gitea: https://gitea.io/en-US/
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
This is very similar to gogs helm chart, with subtle differences.