Add initial Kubernetes config files #7
No reviewers
Labels
No Label
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
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/gitea.kosmos.org#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/6-kubernetes_config"
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?
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_secrets
downloads the secrets to the local filesystem so they can be edited./script/replace_secrets
deletes 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