missing examples for additional secret config sources #286
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#286
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Hi,
I tried to move the database and mail credentials into a seperate secret. For example the database credentials:
The secret is included via
additionalConfigSources
:The
database
section of theapp.ini
contains only values which must not be protected.If i deploy this configuration, I get an
Init:CrashLoopBackOff
error. There is only one example to includeapp.ini
configurations viagitea-app-ini-plaintext
. Unfortunately none with a secret. It would be great if someone here could help me and expand the README for an example with an additionalConfig as secret.It seems that the bug is already known, because I also use an external database.
#279
Hi @volker.raschek. The expected data structure inside a Kubernetes secret and Kubernetes ConfigMap are identical.
Both types are mounted as files into the container. Your secret needs to look like the following:
The key
database
must match the section key insideapp.ini
and represents a file during ini creation. Let me know if this structure works for you. It should. ?I see that the documentation is not as explaining as hoped. Will update the docs according to that requirement.
Hi @justusbunsi,
I adapted my secret. The
database
key was invalid. I tried to deploy gitea again with the credentials stored as secret. I received an other error from an init-container, that the database setting is invalid:The secret looks like your example above. I don't know why it does not work. Any idea?
Oh. I forgot to change one little but important thing in my snippet. The : need to be =.
Please try this again.
Hi @justusbunsi,
this works. Thanks a lot for your help.
I think this should be documented to avoid issues related to this topic in future.
Volker