Add initial Kubernetes config files #7
Labels
Clear labels
bug
dev environment
docs
duplicate
enhancement
feature
idea
invalid
kredits-1
kredits-2
kredits-3
ops
question
security
ui/ux
wontfix
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
Something is not working
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Looking for an answer
All your base are belong to us
User interface, process design, etc.
This won't be fixed
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
No labels
Milestone
No items
No Milestone
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/gitea.kosmos.org#7
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This includes all the resources currently running on https://gitea.kosmos.org
It sets up a persistent data volume for the MySQL database, one for the Gitea data, that Gitea calls the custom folder (config, attachment, avatars, logs, etc). We mount that persistent data volume as /data/gitea. It also creates a Let's Encrypt certificate for gitea.kosmos.org, also saved to the custom folder.
This also includes two scripts:
./script/get_secretsdownloads the secrets to the local filesystem so they can be edited./script/replace_secretsdeletes the remote secrets and creates them again from the local ones in kubernetes/config/*Closes #6
What initial setup would that be? Wouldn't the ini be there from the very start now?
That seems like not a lot of space for git repos. Can it be increased with an existing volume later on? Should it be more from the start?
Very cool! I used the scripts to get the configs, edited them a bit (disabled OpenID and creating orgs for example), then pushed them back and applied the server. All worked flawlessly.
Good job! 👍
Right, I think we can remove all these environment variables
Volumes can be expanded later (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims), the 1GB size is something I used when I was setting everything up initially and forgot to change, it should indeed be higher
Update: as discussed on IRC, just changing the secrets isn't actually enough to re-deploy and apply them. Need to change the deployment config for that.
I have changed the script that replaces the secrets to patch the deployment, causing the pod to restart
What happened to removing the obsolete env vars? I just found them in master.
Just done in #9