ae8d6a6cf3
This is using haproxy-ingress to support forwarding SSH on port 22 Since we're using cert-manager with ingress to get Let's Encrypt certs, we're not using the Let's Encrypt functionality that's part of Gitea. To run this we need to change the config file, have Gitea run on port 3000 as HTTP and disable all the Let's Encrypt config keys. Currently the gitea-ingress.yaml uses the letsencrypt-staging ClusterIssuer This has been tested on a local Kubernetes cluster using Docker for Mac
gitea.kosmos.org
This repository contains configuration files and other assets, that are used to deploy and operate this Gitea instance.
To create a new image containing the customizations:
Edit packer/custom.json to increment the tag, then run this script (needs
Packer in your path)
./script/build_customizations_image
Then edit kubernetes/gitea-server.yaml to use the new tag
(image: eu.gcr.io/fluted-magpie-218106/gitea_custom:$VERSION) and apply the
change:
cd kubernetes
kubectl apply -f gitea-server.yaml
Feel free to open issues for questions, suggestions, bugs, to-do items, and whatever else you want to discuss or resolve.