Add image.fullOverride
#550
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature-decouple-rootless"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the change
This PR is a continuation of the work done by @dgershman in 534, to allow users to override the image from the default rootless behavior of appending
-rootless
to the end of the image tag.Benefits
Allows more flexibility to use externally maintained images that are rootless but don't follow the
-rootless
tag convention.Applicable issues
Additional information
No breaking changes. This does not affect the
image.rootless
conditional checks or the current behavior if someone still wants to rely on the chart to append-rootless
.Checklist
values.yaml
and added to theREADME.md
using readme-generator-for-helmREADME.md
Thanks! Also for adding tests. I think one important thing to add would be an entry to README which lists the adaptions users need to make when providing their own rootless image and running
rootless: false
. Or, phrased differently, we should make it explicit what usingrootless: true
does behind the scences. They could be added in a new subsection below https://gitea.com/gitea/helm-chart#user-content-configuration. AFAICS these are:$HOME
to/data/gitea/git
START_SSH_SERVER: true
SSH_LISTEN_PORT: 2222
SSH_LOG_LEVEL
Other actions, like chowning
/data
are only important when running rootful.@justusbunsi Feel free to add tasks in case I forgot some actions.
@pat-s thank you for the feedback. I just pushed and update based on your suggestion. Not sure if I really hit the mark with what you're wanting but just let me know what you think should be altered and if i got the location wrong and I'm happy to make those changes.
Thanks for continuing the work of #534.
Please update the table-of-content at the top of this document.
Suggestion:
Referring to the new option makes it more obvious why this is an important information.
Be careful with referencing specific lines of code. They tend to get outdated or incomplete quite fast. Instead, let the user look for contexts:
see [deployment.yaml](./templates/gitea/deployment.yaml) template inside (init-)container "env" declarations
.Changing
SSH_LOG_LEVEL
is only possible via Chart logic when not usingrootless
images. See7de8e83433/templates/gitea/deployment.yaml (L270)
for the condition.@ -1279,4 +1106,3 @@
```
<!-- prettier-ignore-start -->
<!-- markdownlint-disable-next-line -->
The empty lines between
<!-- markdownlint-disable-next-line -->
(4x) causes the build to fail. Please remove these empty lines. They are probably added automatically.Kudos for demonstrating how and ensuring that the
image.digest
field is completely ignored when usingimage.fullOverride
.Thanks! I was thinking of even adding the registry, repository, and tag. Do you think that's worth doing, or is digest enough?
That would be great. You can even add a code comment that this purposely set to ensure such behavior.
Suggestion:
This makes it more obvious that the Chart logic still rely on that setting, even when
image.fullOverride
is used. And gives a hint to the new section.Thank you for the awesome feedback and suggestions @justusbunsi.
If I got your intention right, are trying to say that the
SSH_LOG_LEVEL
environment variable is not injected into the container when using a rootless image. If that's the case, I suggest writing it that way. The current "DefiningSSH_LOG_LEVEL
turned off" sounds a bit off.Awesome 🚀
@pat-s Anything left from your side?
I'll add some post-merge wording and formatting updates but overall 👍 Thanks everyone!